{"id":"CVE-2025-68282","summary":"usb: gadget: udc: fix use-after-free in usb_gadget_state_work","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nusb: gadget: udc: fix use-after-free in usb_gadget_state_work\n\nA race condition during gadget teardown can lead to a use-after-free\nin usb_gadget_state_work(), as reported by KASAN:\n\n  BUG: KASAN: invalid-access in sysfs_notify+0x2c/0xd0\n  Workqueue: events usb_gadget_state_work\n\nThe fundamental race occurs because a concurrent event (e.g., an\ninterrupt) can call usb_gadget_set_state() and schedule gadget-\u003ework\nat any time during the cleanup process in usb_del_gadget().\n\nCommit 399a45e5237c (\"usb: gadget: core: flush gadget workqueue after\ndevice removal\") attempted to fix this by moving flush_work() to after\ndevice_del(). However, this does not fully solve the race, as a new\nwork item can still be scheduled *after* flush_work() completes but\nbefore the gadget's memory is freed, leading to the same use-after-free.\n\nThis patch fixes the race condition robustly by introducing a 'teardown'\nflag and a 'state_lock' spinlock to the usb_gadget struct. The flag is\nset during cleanup in usb_del_gadget() *before* calling flush_work() to\nprevent any new work from being scheduled once cleanup has commenced.\nThe scheduling site, usb_gadget_set_state(), now checks this flag under\nthe lock before queueing the work, thus safely closing the race window.","modified":"2026-04-02T13:03:29.723933Z","published":"2025-12-16T15:06:04.332Z","related":["MGASA-2026-0017","MGASA-2026-0018"],"database_specific":{"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/68xxx/CVE-2025-68282.json","cna_assigner":"Linux"},"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/10014310193cf6736c1aeb4105c5f4a0818d0c65"},{"type":"WEB","url":"https://git.kernel.org/stable/c/3b32caa73d135eea8fb9cabb45e9fc64c5a3ecb9"},{"type":"WEB","url":"https://git.kernel.org/stable/c/baeb66fbd4201d1c4325074e78b1f557dff89b5b"},{"type":"WEB","url":"https://git.kernel.org/stable/c/c12a0c3ef815ddd67e47f9c819f9fe822fed5467"},{"type":"WEB","url":"https://git.kernel.org/stable/c/dddc944d65169b552e09cb54e3ed4fbb9ea26416"},{"type":"WEB","url":"https://git.kernel.org/stable/c/eee16f3ff08e759ea828bdf7dc1c0ef2f22134f5"},{"type":"WEB","url":"https://git.kernel.org/stable/c/f02a412c0a18f02f0f91b0a3d9788315a721b7fd"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/68xxx/CVE-2025-68282.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68282"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"5702f75375aa9ecf8ad3431aef3fe6ce8c8dbd15"},{"fixed":"dddc944d65169b552e09cb54e3ed4fbb9ea26416"},{"fixed":"eee16f3ff08e759ea828bdf7dc1c0ef2f22134f5"},{"fixed":"c12a0c3ef815ddd67e47f9c819f9fe822fed5467"},{"fixed":"f02a412c0a18f02f0f91b0a3d9788315a721b7fd"},{"fixed":"10014310193cf6736c1aeb4105c5f4a0818d0c65"},{"fixed":"3b32caa73d135eea8fb9cabb45e9fc64c5a3ecb9"},{"fixed":"baeb66fbd4201d1c4325074e78b1f557dff89b5b"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-68282.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.12.0"},{"fixed":"5.10.248"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.11.0"},{"fixed":"5.15.198"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.1.159"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.119"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.61"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.17.11"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-68282.json"}}],"schema_version":"1.7.5"}