Heimdall Security Logo

CVE-2025-68287

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <3.2, <=6.12.*, <fa5eaf701e576880070b60922200557ae4aa54e1, 0, <67192e8cb7f941b5bba91e4bb290683576ce1607, <afc0e34f161ce61ad351303c46eb57bd44b8b090, 6.18, 5.10.247, <=5.10.*, <=6.6.*, 72246da40f3719af3bfd104a2365b32537c27d83, <e4037689a366743c4233966f0e74bc455820d316, 3.2, 5.15.197, 6.1.159, 6.6.119, 6.17.11, <=*, <=5.15.*, <=6.17.*, <467add9db13219101f14b6cc5477998b4aaa5fe2, <47de14d741cc4057046c9e2f33df1f7828254e6c, <7cfb62888eba292fa35cd9ddbd28ce595f60e139, 6.12.61

Description

In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: Fix race condition between concurrent dwc3_remove_requests() call paths This patch addresses a race condition caused by unsynchronized execution of multiple call paths invoking `dwc3_remove_requests()`, leading to premature freeing of USB requests and subsequent crashes. Three distinct execution paths interact with `dwc3_remove_requests()`: Path 1: Triggered via `dwc3_gadget_reset_interrupt()` during USB reset handling. The call stack includes: - `dwc3_ep0_reset_state()` - `dwc3_ep0_stall_and_restart()` - `dwc3_ep0_out_start()` - `dwc3_remove_requests()` - `dwc3_gadget_del_and_unmap_request()` Path 2: Also initiated from `dwc3_gadget_reset_interrupt()`, but through `dwc3_stop_active_transfers()`. The call stack includes: - `dwc3_stop_active_transfers()` - `dwc3_remove_requests()` - `dwc3_gadget_del_and_unmap_request()` Path 3: Occurs independently during `adb root` execution, which triggers USB function unbind and bind operations. The sequence includes: - `gserial_disconnect()` - `usb_ep_disable()` - `dwc3_gadget_ep_disable()` - `dwc3_remove_requests()` with `-ESHUTDOWN` status Path 3 operates asynchronously and lacks synchronization with Paths 1 and 2. When Path 3 completes, it disables endpoints and frees 'out' requests. If Paths 1 or 2 are still processing these requests, accessing freed memory leads to a crash due to use-after-free conditions. To fix this added check for request completion and skip processing if already completed and added the request status for ep0 while queue.

Gravité et risque d'exploitation

CVE-2025-68287 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. 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 13.1 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <3.2, <=6.12.*, <fa5eaf701e576880070b60922200557ae4aa54e1, 0, <67192e8cb7f941b5bba91e4bb290683576ce1607, <afc0e34f161ce61ad351303c46eb57bd44b8b090, 6.18, 5.10.247, <=5.10.*, <=6.6.*, 72246da40f3719af3bfd104a2365b32537c27d83, <e4037689a366743c4233966f0e74bc455820d316, 3.2, 5.15.197, 6.1.159, 6.6.119, 6.17.11, <=*, <=5.15.*, <=6.17.*, <467add9db13219101f14b6cc5477998b4aaa5fe2, <47de14d741cc4057046c9e2f33df1f7828254e6c, <7cfb62888eba292fa35cd9ddbd28ce595f60e139, 6.12.61) 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