Linux Kernel USB Gadget UAF in usb_gadget_state_work (CVE-2025-68282)
CVE-2025-68282 Published on December 16, 2025
usb: gadget: udc: fix use-after-free in usb_gadget_state_work
In the Linux kernel, the following vulnerability has been resolved:
usb: gadget: udc: fix use-after-free in usb_gadget_state_work
A race condition during gadget teardown can lead to a use-after-free
in usb_gadget_state_work(), as reported by KASAN:
BUG: KASAN: invalid-access in sysfs_notify+0x2c/0xd0
Workqueue: events usb_gadget_state_work
The fundamental race occurs because a concurrent event (e.g., an
interrupt) can call usb_gadget_set_state() and schedule gadget->work
at any time during the cleanup process in usb_del_gadget().
Commit 399a45e5237c ("usb: gadget: core: flush gadget workqueue after
device removal") attempted to fix this by moving flush_work() to after
device_del(). However, this does not fully solve the race, as a new
work item can still be scheduled *after* flush_work() completes but
before the gadget's memory is freed, leading to the same use-after-free.
This patch fixes the race condition robustly by introducing a 'teardown'
flag and a 'state_lock' spinlock to the usb_gadget struct. The flag is
set during cleanup in usb_del_gadget() *before* calling flush_work() to
prevent any new work from being scheduled once cleanup has commenced.
The scheduling site, usb_gadget_set_state(), now checks this flag under
the lock before queueing the work, thus safely closing the race window.
Products Associated with CVE-2025-68282
stack.watch emails you whenever new vulnerabilities are published in Linux Kernel or Linux Kernel. Just hit a watch button to start following.
Affected Versions
Linux:- Version 5702f75375aa9ecf8ad3431aef3fe6ce8c8dbd15 and below dddc944d65169b552e09cb54e3ed4fbb9ea26416 is affected.
- Version 5702f75375aa9ecf8ad3431aef3fe6ce8c8dbd15 and below eee16f3ff08e759ea828bdf7dc1c0ef2f22134f5 is affected.
- Version 5702f75375aa9ecf8ad3431aef3fe6ce8c8dbd15 and below c12a0c3ef815ddd67e47f9c819f9fe822fed5467 is affected.
- Version 5702f75375aa9ecf8ad3431aef3fe6ce8c8dbd15 and below f02a412c0a18f02f0f91b0a3d9788315a721b7fd is affected.
- Version 5702f75375aa9ecf8ad3431aef3fe6ce8c8dbd15 and below 10014310193cf6736c1aeb4105c5f4a0818d0c65 is affected.
- Version 5702f75375aa9ecf8ad3431aef3fe6ce8c8dbd15 and below 3b32caa73d135eea8fb9cabb45e9fc64c5a3ecb9 is affected.
- Version 5702f75375aa9ecf8ad3431aef3fe6ce8c8dbd15 and below baeb66fbd4201d1c4325074e78b1f557dff89b5b is affected.
- Version 3.12 is affected.
- Before 3.12 is unaffected.
- Version 5.10.248, <= 5.10.* is unaffected.
- Version 5.15.198, <= 5.15.* is unaffected.
- Version 6.1.159, <= 6.1.* is unaffected.
- Version 6.6.119, <= 6.6.* is unaffected.
- Version 6.12.61, <= 6.12.* is unaffected.
- Version 6.17.11, <= 6.17.* is unaffected.
- Version 6.18, <= * is unaffected.
Exploit Probability
EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.