CVE-2026-99776: net/9p/usbg: clear stale client pointer on close
In the Linux kernel, the following vulnerability has been resolved:
net/9p/usbg: clear stale client pointer on close
p9usbgclose() tears down the client transport, but usb9pfs keeps using usb9pfs->client from asynchronous TX and RX completion handlers. A late completion can therefore dereference a client that has already been freed during mount teardown.
Clear usb9pfs->client under usb9pfs->lock when closing the transport, detach any pending TX request from inreq->context, and make the TX/RX completion handlers bail out once the transport has been detached. This keeps late completions from touching a freed or rebound p9client.
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
In p9_usbg_close(), clear usb9pfs->client under usb9pfs->lock, detach any pending TX request from in_req->context, and make TX/RX completion handlers bail out after the transport is detached.
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
Systems using the Linux kernel's net/9p/usbg transport are exposed when that transport is torn down while asynchronous USB 9p TX or RX completions can still occur. The issue is associated with mount teardown and late completion handling.
What condition triggers the vulnerable use-after-free?
A client transport must be closed and its p9_client freed while an asynchronous TX or RX completion handler still accesses usb9pfs->client. A late completion can then dereference the freed or rebound client pointer.
How can this be mitigated if the fix cannot be applied immediately?
The provided information does not identify a configuration workaround. Reducing or avoiding use of the net/9p/usbg transport and avoiding its mount teardown path would avoid the described condition.
How can I determine whether a system has the fix?
Check whether the kernel includes a change that clears usb9pfs->client under usb9pfs->lock during close, detaches pending TX requests from in_req->context, and makes TX/RX completion handlers stop after transport detachment. The listed stable references identify commits containing the resolution.