CVE-2025-68287 usb: dwc3: Fix race condition between concurrent dwc3_remove_requests() call paths

Not scored Published Updated

A race condition in the Linux kernel DWC3 USB driver allows local attackers to cause a system crash via use-after-free during concurrent USB request removal.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2025-68287?

CVE-2025-68287 is a vulnerability in Linux, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

Official 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.

Which versions are affected by CVE-2025-68287?

How do I fix CVE-2025-68287?

Apply the vendor's patch.

Is CVE-2025-68287 being exploited?

There is no known exploitation of CVE-2025-68287 in the wild and no public exploit code.

Sources

Also known as BELL-CVE-2025-68287, DEBIAN-CVE-2025-68287, GHSA-23wc-qh4p-pmrr, ROOT-OS-DEBIAN-12-CVE-2025-68287, ROOT-OS-DEBIAN-13-CVE-2025-68287, ROOT-OS-UBUNTU-2204-CVE-2025-68287 and 2 more.

Is CVE-2025-68287 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free