Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-93214 Overview
CVE-2026-93214 is a locking defect in the Linux kernel USB gadget subsystem, specifically the Target Core Module function driver (f_tcm). The function usbg_make_tpg() held dep_lock while calling configfs_depend_item_unlocked(), which acquires the configfs root inode lock across subsystems. This created a circular lock dependency with configfs_rmdir() of the form dep_lock -> configfs root inode lock -> su_mutex -> dep_lock. Triggering the condition deadlocks kernel threads interacting with the USB gadget configfs interface, leading to denial of service on affected systems.
Critical Impact
Local privileged operations against the USB gadget configfs hierarchy can deadlock kernel tasks, hanging the subsystem until reboot.
Affected Products
- Linux kernel versions containing the usb: gadget: f_tcm driver prior to the fix commits
- Distributions shipping stable kernels that include the pre-patch usbg_make_tpg() implementation
- Embedded and server systems that enable USB gadget target mode with configfs
Discovery Timeline
- 2026-09-24 - CVE CVE-2026-93214 published to NVD
- 2026-09-24 - Last updated in NVD database
Technical Details for CVE-2026-93214
Vulnerability Analysis
The defect lives in drivers/usb/gadget/function/f_tcm.c. When userspace creates a Target Portal Group through configfs, usbg_make_tpg() acquires dep_lock and then calls configfs_depend_item_unlocked(). The depend path takes the configfs root inode lock to traverse across subsystems, which can later re-enter paths that acquire su_mutex and dep_lock again.
Concurrently, configfs_rmdir() on a related object walks the same locks in a different order. The resulting lock chain dep_lock -> configfs root inode lock -> su_mutex -> dep_lock forms a circular dependency. Lockdep flags this as a classic AB-BA deadlock, and under contention the kernel threads block indefinitely.
Root Cause
The root cause is incorrect lock scope. In usbg_make_tpg(), dep_lock only protected a read of opts->ready, a flag that is set exactly once by tcm_set_name() and never reset. Holding a mutex to read a monotonic boolean while invoking a cross-subsystem configfs API that takes heavier locks introduces an unnecessary ordering constraint and the circular dependency. This is a race condition and deadlock defect in kernel locking logic rather than a memory safety issue.
Attack Vector
Exploitation requires local access with permissions to manipulate the USB gadget configfs tree, typically root or a container with the relevant mounts. A user triggers concurrent mkdir and rmdir operations on tpg entries under the f_tcm function, inducing the lock inversion. There is no evidence of remote exploitation, no public proof-of-concept, and the EPSS data indicates a low probability of exploitation activity. The impact is denial of service through hung kernel tasks, not code execution or data disclosure.
No verified exploit code is published. Technical details are available in the upstream fix commits, including Kernel Commit 78a14ea2 and Kernel Commit f81a2da1.
Detection Methods for CVE-2026-93214
Indicators of Compromise
- Hung task warnings in dmesg referencing usbg_make_tpg, configfs_depend_item_unlocked, or configfs_rmdir
- Lockdep reports (possible circular locking dependency detected) naming dep_lock and su_mutex
- Processes stuck in D state while performing mkdir/rmdir under the USB gadget configfs mount
Detection Strategies
- Enable CONFIG_PROVE_LOCKING on test kernels and monitor for lockdep splats involving the f_tcm driver
- Collect kernel logs centrally and alert on hung_task_timeout_secs events referencing configfs or gadget function paths
- Inventory kernel versions across Linux fleets and flag hosts running pre-patch builds that enable the f_tcm driver
Monitoring Recommendations
- Forward /var/log/kern.log and journalctl -k output to a central logging platform for pattern matching on lock warnings
- Track USB gadget configfs mount usage on servers and embedded devices to scope exposure
- Review kernel package versions during routine vulnerability scans and correlate with the fix commits listed in the NVD entry
How to Mitigate CVE-2026-93214
Immediate Actions Required
- Apply the upstream stable kernel update that removes dep_lock from usbg_make_tpg() and switches opts->ready access to READ_ONCE/WRITE_ONCE
- Restrict access to USB gadget configfs mounts to trusted administrators and avoid exposing them inside unprivileged containers
- Reboot after patching to ensure the vulnerable module is unloaded and replaced
Patch Information
The fix is distributed across several stable branches. Reference the upstream commits for the exact change: Kernel Commit 3639438a, Kernel Commit 6bcd9ee6, Kernel Commit 78a14ea2, Kernel Commit 9dbf74f4, Kernel Commit abad5daa, Kernel Commit d90b0f90, Kernel Commit eef3e62f, and Kernel Commit f81a2da1. Install the vendor-supplied kernel package that includes the backport for your distribution.
Workarounds
- Unload the usb_f_tcm module on systems that do not require USB gadget target mode (modprobe -r usb_f_tcm)
- Blacklist the usb_f_tcm module in /etc/modprobe.d/ on hosts where USB gadget target functionality is not needed
- Avoid issuing concurrent mkdir/rmdir operations against f_tcm TPG entries until the patched kernel is deployed
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

