CVE-2026-99783: net/9p/usbg: Fix use-after-free in disable_usb9pfs()
In the Linux kernel, the following vulnerability has been resolved:
net/9p/usbg: Fix use-after-free in disableusb9pfs()
disableusb9pfs() frees the IN and OUT usbrequest objects before it disables the corresponding endpoints. If either request is still queued, the later usbepdisable() call cancels the endpoint queue and the UDC driver can still access the already freed request.
With dummyhcd and KASAN, this is reproducible by queueing the OUT request and then disconnecting the configfs gadget:
BUG: KASAN: slab-use-after-free in dummydisable+0x2b4/0x300 Read of size 8 at addr ffff888009702400 by task sh/1 usbepdisable+0x8e/0x1f0 usb9pfsfuncunbind+0x193/0x350 gadgetdevdescUDCstore+0x135/0x280
dummyfreerequest() also warns because the request is freed while its queue entry is still linked.
Disable both endpoints before freeing the request objects. This lets usbepdisable() cancel any queued transfers and invoke the completion callback while the request storage is still valid. The request objects are then freed only after they have been removed from the endpoint queues.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 7.3.5-1 - Compensating control
Disable both endpoints before freeing the IN and OUT usb_request objects, so queued transfers are canceled and completion callbacks run while the request storage is still valid.
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
Systems using the Linux USB gadget implementation for usb9pfs are exposed when the gadget is unbound or disconnected while an IN or OUT USB request remains queued. The reported reproduction uses a configfs gadget with dummy_hcd.
What condition is required to trigger the use-after-free?
A USB request must still be queued when the relevant endpoint is disabled during gadget teardown. The endpoint-disable operation cancels queued transfers, and the USB device-controller driver may access a request that was already freed.
How can I identify a likely occurrence?
With KASAN enabled, the issue can produce a slab-use-after-free report in dummy_disable through usb_ep_disable during usb9pfs_func_unbind. The dummy controller may also warn that a request was freed while its queue entry remained linked.