CVE-2026-99778: net/9p/usbg: fix out_req buffer leak in disable_usb9pfs
In the Linux kernel, the following vulnerability has been resolved:
net/9p/usbg: fix outreq buffer leak in disableusb9pfs
usb9pfs->outreq is allocated with allocepreq(), which also allocates the request's data buffer (req->buf). disableusb9pfs() frees it with plain usbepfreerequest(), which only frees the usbrequest structure itself and leaks req->buf on every close.
Use freeepreq() instead, matching the allocator, as documented by its own comment ("Requests allocated via allocepreq() must be freed by freeepreq()").
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
Event History
Frequently Asked Questions
Under what conditions does the memory leak occur?
The leak occurs each time usb9pfs is closed. The affected path allocates usb9pfs->out_req with alloc_ep_req() and releases it with usb_ep_free_request(), leaving the request data buffer allocated.
What is the corrective change?
The request must be released with free_ep_req() rather than usb_ep_free_request(). free_ep_req() matches alloc_ep_req() and frees both the USB request structure and its associated data buffer.