CVE-2026-99784: 9p/xen: fix refcount leak in p9_xen_response() on wrong tag

Published Nov 20, 2026
·
Updated

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

8 affected componentsFixes available
linux/kernel>=4.19.57<4.20
4.20
linux/kernel>=4.20.0<6.12.118
6.12.118
linux/kernel>=6.13.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5
debian/linux*
debian/linux*
debian/linux*
debian/linux<=6.1.176-1, <=6.1.192-2, <=6.12.107-1, <=6.12.117-1, <=7.3.4-1
7.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 4.20
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  4. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  5. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 7.3.5-1
  6. 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

Nov 20, 2026
CVE Published
via MITRE·05:51 AM
Data Sourced
via MITRE·05:51 AM
Description
Data Sourced
via OSV·05:51 AM
DescriptionAffected Software
Data Sourced
via NVD·06:18 AM
Description

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203