Back to CVE records
Not yet scoredPublished Sep 11, 2026

CVE-2026-89732usb: gadget: f_fs: Prevent deadlock during ep0 read loop

Updated under an hour ago ()

Does this affect you?

It affects Linux. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_fs: Prevent deadlock during ep0 read loop Currently, ffs_ep0_read() holds ffs->mutex when it prepares to go to sleep waiting for an event. When no setup events are pending, it calls wait_event_interruptible_exclusive_locked_irq() with the mutex still held. The wait macro deliberately drops the waitqueue spinlock before sleeping but does not drop the mutex. If a userspace daemon is polling ep0 via read() and the gadget is asynchronously torn down via configfs (e.g., echo "" > UDC), a deadlock can occur: 1. The configfs teardown calls functionfs_unbind(), which queues a FUNCTIONFS_UNBIND event. 2. The daemon wakes up, consumes the event, and drops the mutex. 3. However, if the daemon loops and immediately issues another read() before exiting, it reacquires ffs->mutex and again goes into an interruptible sleep. 4. Meanwhile, functionfs_unbind() continues execution and attempts to acquire ffs->mutex to tear down ep0req. 5. The kernel deadlocks because the configfs thread is stuck in an uninterruptible sleep waiting for the mutex, while the userspace daemon is in an interruptible sleep holding the mutex forever because no more events will arrive. To fix this, we drop both the waitqueue spinlock and ffs->mutex before going to sleep, and use wait_event_interruptible_exclusive() instead. Upon waking up, we jump back to the `retry` label to safely reacquire the mutex and re-evaluate the state machine. By not sleeping with ffs->mutex held, we natively decouple gadget teardowns (which require the mutex) from userspace polling.

CVSS
Not yet scored
Weakness (CWE)
Not given
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Linux
NVD analysis
Received
Record last updated
Sep 14, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
Linux Linux
linux:linux (from the name)
from ddf8abd2599491cbad959c700b90ba72a5dce8d0 before fbe3db4b650c284df8eb4cb68eebcf270cf861b5; from ddf8abd2599491cbad959c700b90ba72a5dce8d0 before 30430509c156e1df2bdafd5f1cadb160e53db5d6; from ddf8abd2599491cbad959c700b90ba72a5dce8d0 before bafddd0f20b5228760be303aa69c58502e92309c; from ddf8abd2599491cbad959c700b90ba72a5dce8d0 before b0a6bfac0c3c3edf5b2ecaee87a09234601fe78d; from ddf8abd2599491cbad959c700b90ba72a5dce8d0 before fd20cc68bbdb5620696ac108e8f2efd180fe2c1a; from ddf8abd2599491cbad959c700b90ba72a5dce8d0 before 34e88f53614640b59039a46717fb6142e9871022; from ddf8abd2599491cbad959c700b90ba72a5dce8d0 before eac233e63f9db82ba874e3cccafaafab162999e0; from ddf8abd2599491cbad959c700b90ba72a5dce8d0 before 569dd7e5dcffe1e1c6b26ca2cd3be57eb433e082
CNA record

References

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.