Heimdall Security Logo

CVE-2024-56670

Vulnérabilité moyenne dans Linux (Linux)

CVSS 5.5 · Moyenne
EPSS 0.2%
Linux•Linux•Versions : 6.13, <=6.1.*, <=6.12.*, <1247e1df086aa6c17ab53cd1bedce70dd7132765, 5.15.175, <4cfbca86f6a8b801f3254e0e3c8f2b1d2d64be2b, 6.1.121, 0, <2.6.27, <8ca07a3d18f39b1669927ef536e485787e856df6, 5.4.288, <=5.10.*, <=6.6.*, c1dca562be8ada614ef193aa246c6f8705bcd6b9, <=5.4.*, 6.6.67, <dd6b0ca6025f64ccb465a6a3460c5b0307ed9c44, <=*, <c83213b6649d22656b3a4e92544ceeea8a2c6c07, <=5.15.*, <28b3c03a6790de1f6f2683919ad657840f0f0f58, 6.12.6, <4efdfdc32d8d6307f968cd99f1db64468471bab1, 5.10.232, 2.6.27

Description

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: u_serial: Fix the issue that gs_start_io crashed due to accessing null pointer Considering that in some extreme cases, when u_serial driver is accessed by multiple threads, Thread A is executing the open operation and calling the gs_open, Thread B is executing the disconnect operation and calling the gserial_disconnect function,The port->port_usb pointer will be set to NULL. E.g. Thread A Thread B gs_open() gadget_unbind_driver() gs_start_io() composite_disconnect() gs_start_rx() gserial_disconnect() ... ... spin_unlock(&port->port_lock) status = usb_ep_queue() spin_lock(&port->port_lock) spin_lock(&port->port_lock) port->port_usb = NULL gs_free_requests(port->port_usb->in) spin_unlock(&port->port_lock) Crash This causes thread A to access a null pointer (port->port_usb is null) when calling the gs_free_requests function, causing a crash. If port_usb is NULL, the release request will be skipped as it will be done by gserial_disconnect. So add a null pointer check to gs_start_io before attempting to access the value of the pointer port->port_usb. Call trace: gs_start_io+0x164/0x25c gs_open+0x108/0x13c tty_open+0x314/0x638 chrdev_open+0x1b8/0x258 do_dentry_open+0x2c4/0x700 vfs_open+0x2c/0x3c path_openat+0xa64/0xc60 do_filp_open+0xb8/0x164 do_sys_openat2+0x84/0xf0 __arm64_sys_openat+0x70/0x9c invoke_syscall+0x58/0x114 el0_svc_common+0x80/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x38/0x68

Gravité et risque d'exploitation

CVE-2024-56670 obtient un score CVSS de 5.5/10, soit une gravité moyenne. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.23 %, ce qui la place devant 12.5 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 6.13, <=6.1.*, <=6.12.*, <1247e1df086aa6c17ab53cd1bedce70dd7132765, 5.15.175, <4cfbca86f6a8b801f3254e0e3c8f2b1d2d64be2b, 6.1.121, 0, <2.6.27, <8ca07a3d18f39b1669927ef536e485787e856df6, 5.4.288, <=5.10.*, <=6.6.*, c1dca562be8ada614ef193aa246c6f8705bcd6b9, <=5.4.*, 6.6.67, <dd6b0ca6025f64ccb465a6a3460c5b0307ed9c44, <=*, <c83213b6649d22656b3a4e92544ceeea8a2c6c07, <=5.15.*, <28b3c03a6790de1f6f2683919ad657840f0f0f58, 6.12.6, <4efdfdc32d8d6307f968cd99f1db64468471bab1, 5.10.232, 2.6.27) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE