CVE-2026-64346usb: gadget: udc: Fix use-after-free in gadget_match_driver
Updated under an hour ago ()
Does this affect you?
It affects Linux and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: udc: Fix use-after-free in gadget_match_driver The udc structure acts as the management structure for the gadget, but their lifecycles are decoupled. A race condition exists where usb_del_gadget() frees the udc memory (e.g., via mode-switch work) while gadget_match_driver() concurrently accesses the freed udc memory (e.g., via configfs), causing a Use-After-Free (UAF) that triggers a NULL pointer dereference when the freed memory is zeroed: [39430.908615][ T1171] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 [39430.911397][ T1171] pc : __pi_strcmp+0x20/0x140 [39430.911441][ T1171] lr : gadget_match_driver+0x34/0x60 ... [39430.911890][ T1171] usb_gadget_register_driver_owner+0x50/0xf8 [39430.911910][ T1171] gadget_dev_desc_UDC_store+0xf4/0x140 [39430.931308][ T1171] configfs_write_iter+0xec/0x134 [39430.957058][ T1171] Workqueue: events_freezable __dwc3_set_mode [39430.957287][ T1171] dwc3_gadget_exit+0x34/0x8c [39430.957304][ T1171] __dwc3_set_mode+0xc0/0x664 Fix this by ensuring the udc structure remains allocated until the gadget is released. To achieve this, introduce a new usb_gadget_release() routine to the core. When the gadget is added, usb_add_gadget() stores the gadget's release routine in the udc structure and takes a reference to the udc. When the gadget is released, usb_gadget_release() drops the reference to the udc and then calls the gadget's release routine.
- CVSS
- 7.8 HIGH (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- 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
- Analyzed
- Record last updated
- Aug 17, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from fc274c1e997314bf47f6a62c79b5d7e554ed59c4 before 50eeb8e8a4f389efc91b93cff14a683e714ec194; from fc274c1e997314bf47f6a62c79b5d7e554ed59c4 before 7a5214dae906d9f58e07bc4995e8181ee74439f4; from fc274c1e997314bf47f6a62c79b5d7e554ed59c4 before d026f71df141c9b064ff32a78af5391a31ef75c2; from fc274c1e997314bf47f6a62c79b5d7e554ed59c4 before b52476a83d9e12df00765359d728a875b128bef1; from fc274c1e997314bf47f6a62c79b5d7e554ed59c4 before 54fa390aae393eb130f307a85562e3001cc39a52; from fc274c1e997314bf47f6a62c79b5d7e554ed59c4 before 67e511d2989eb1c8c588b599ce2fcc6bb8e6f7ea | CNA record |
linux linux_kernel linux:linux_kernel | from 5.19 before 6.1.178; from 6.2 before 6.6.145; from 6.7 before 6.12.96; from 6.13 before 6.18.39; from 6.19 before 7.1.4; 7.2; 7.2 | NVD |
References
- https://git.kernel.org/stable/c/50eeb8e8a4f389efc91b93cff14a683e714ec194patch
- https://git.kernel.org/stable/c/7a5214dae906d9f58e07bc4995e8181ee74439f4patch
- https://git.kernel.org/stable/c/d026f71df141c9b064ff32a78af5391a31ef75c2patch
- https://git.kernel.org/stable/c/b52476a83d9e12df00765359d728a875b128bef1patch
- https://git.kernel.org/stable/c/54fa390aae393eb130f307a85562e3001cc39a52patch
- https://git.kernel.org/stable/c/67e511d2989eb1c8c588b599ce2fcc6bb8e6f7eapatch
The CVE record on cve.org NVD's entry
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.