CVE-2026-99784: 9p/xen: fix refcount leak in p9_xen_response() on wrong tag
In the Linux kernel, the following vulnerability has been resolved:
9p/xen: fix refcount leak in p9xenresponse() on wrong tag
p9xenresponse() looks up the request for an incoming reply with p9taglookup(), which takes a reference on the returned p9reqt. When the tag does not resolve to a request in REQSTATUSSENT, the function warns and continues the loop without dropping that reference, permanently leaking the p9reqt and its msize buffers. The reply header, including the tag, is supplied by the backend, so a malicious or buggy 9P backend can leak kernel memory on every crafted response.
Drop the reference before continuing.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 4.20 - 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 7.3.5-1 - Compensating control
In p9_xen_response(), drop the reference before continuing when the tag does not resolve to a request in REQ_STATUS_SENT.
Event History
Frequently Asked Questions
Who can trigger the leak?
A malicious or buggy 9P backend can trigger it by supplying crafted reply headers with tags that resolve to requests not in REQ_STATUS_SENT. The affected path is specifically the Xen 9P transport response handler.
What is the impact of repeated exploitation?
Each crafted response can permanently leak a p9_req_t and its msize buffers in kernel memory. Repeated responses can therefore consume kernel memory over time.
Is the issue caused by an untrusted reply field?
Yes. The backend supplies the reply header, including the tag used to look up the request, so backend-controlled tags reach the affected validation path.
What does the fix change?
The fix drops the reference obtained by p9_tag_lookup() before continuing when the tag does not identify a request in REQ_STATUS_SENT. This prevents the request object and its associated buffers from being retained.