Heimdall Security Logo

CVE-2023-52855

Vulnérabilité moyenne dans Linux (Linux)

CVSS 5.5 · Moyenne
EPSS 0.2%
Linux•Linux•Versions : <fcaafb574fc88a52dce817f039f7ff2f9da38001, <=6.1.*, <a7bee9598afb38004841a41dd8fe68c1faff4e90, <64c47749fc7507ed732e155c958253968c1d275e, <ef307bc6ef04e8c1ea843231db58e3afaafa9fa6, <4.2, 6.6.2, 0, 33ad261aa62be02f0cedeb4d5735cc726de84a3f, 6.5.12, 6.1.63, 5.4.261, <bdb3dd4096302d6b87441fdc528439f171b04be6, 5.10.201, <=5.10.*, <=4.14.*, <=6.6.*, 5.15.139, <=5.4.*, <6b21a22728852d020a6658d39cd7bb7e14b07790, <=4.19.*, <fed492aa6493a91a77ebd51da6fb939c98d94a0d, 4.2, 4.14.330, <=*, <=5.15.*, <=6.5.*, <3e851a77a13ce944d703721793f49ee82622986d, 6.7, <14c9ec34e8118fbffd7f5431814d767726323e72, 4.19.299

Description

In the Linux kernel, the following vulnerability has been resolved: usb: dwc2: fix possible NULL pointer dereference caused by driver concurrency In _dwc2_hcd_urb_enqueue(), "urb->hcpriv = NULL" is executed without holding the lock "hsotg->lock". In _dwc2_hcd_urb_dequeue(): spin_lock_irqsave(&hsotg->lock, flags); ... if (!urb->hcpriv) { dev_dbg(hsotg->dev, "## urb->hcpriv is NULL ##\n"); goto out; } rc = dwc2_hcd_urb_dequeue(hsotg, urb->hcpriv); // Use urb->hcpriv ... out: spin_unlock_irqrestore(&hsotg->lock, flags); When _dwc2_hcd_urb_enqueue() and _dwc2_hcd_urb_dequeue() are concurrently executed, the NULL check of "urb->hcpriv" can be executed before "urb->hcpriv = NULL". After urb->hcpriv is NULL, it can be used in the function call to dwc2_hcd_urb_dequeue(), which can cause a NULL pointer dereference. This possible bug is found by an experimental static analysis tool developed by myself. This tool analyzes the locking APIs to extract function pairs that can be concurrently executed, and then analyzes the instructions in the paired functions to identify possible concurrency bugs including data races and atomicity violations. The above possible bug is reported, when my tool analyzes the source code of Linux 6.5. To fix this possible bug, "urb->hcpriv = NULL" should be executed with holding the lock "hsotg->lock". After using this patch, my tool never reports the possible bug, with the kernelconfiguration allyesconfig for x86_64. Because I have no associated hardware, I cannot test the patch in runtime testing, and just verify it according to the code logic.

Gravité et risque d'exploitation

CVE-2023-52855 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.24 %, ce qui la place devant 14.8 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <fcaafb574fc88a52dce817f039f7ff2f9da38001, <=6.1.*, <a7bee9598afb38004841a41dd8fe68c1faff4e90, <64c47749fc7507ed732e155c958253968c1d275e, <ef307bc6ef04e8c1ea843231db58e3afaafa9fa6, <4.2, 6.6.2, 0, 33ad261aa62be02f0cedeb4d5735cc726de84a3f, 6.5.12, 6.1.63, 5.4.261, <bdb3dd4096302d6b87441fdc528439f171b04be6, 5.10.201, <=5.10.*, <=4.14.*, <=6.6.*, 5.15.139, <=5.4.*, <6b21a22728852d020a6658d39cd7bb7e14b07790, <=4.19.*, <fed492aa6493a91a77ebd51da6fb939c98d94a0d, 4.2, 4.14.330, <=*, <=5.15.*, <=6.5.*, <3e851a77a13ce944d703721793f49ee82622986d, 6.7, <14c9ec34e8118fbffd7f5431814d767726323e72, 4.19.299) 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