CVE-2026-99764: Linux kernel · 9p/xen: validate the response size from the backend
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in c342fef95252c92c46531da676784c833806fd9a : patch Linux kernel soon.
Data as of 20 Nov 2026, 06:19 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in c342fef95252c92c46531da676784c833806fd9a, 79a3d1bfd5b25bd0da01df4a364c113715146970, 9b4cf60c6b739461c5b4ec9c52587da6b2608786 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade Linux kernel to c342fef95252c92c46531da676784c833806fd9a, 79a3d1bfd5b25bd0da01df4a364c113715146970, 9b4cf60c6b739461c5b4ec9c52587da6b2608786 or 0ca38f8aeca45f47123cbf65710b889078558f8a.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in the Linux kernel commits identified by hashes c342fef95252c92c46531da676784c833806fd9a, 79a3d1bfd5b25bd0da01df4a364c113715146970, 9b4cf60c6b739461c5b4ec9c52587da6b2608786, and 0ca38f8aeca45f47123cbf65710b889078558f8a. Users should update their Linux kernel to a version including these fixes to mitigate the issue.
Description
CVE-2026-99764 is a vulnerability in the Linux kernel's 9p/xen subsystem where the response size from the backend is not properly validated. This can cause the consumer index to not advance when a malformed response is received, leading to repeated processing of the same data and potentially a NULL pointer dereference in kernel space. The issue has been fixed by rejecting responses with sizes outside the valid range before processing.
References
- git.kernel.org/stable/c/79a3d1bfd5b25bd0da01df4a364c113715146970 (opens in a new tab)
- git.kernel.org/stable/c/0ca38f8aeca45f47123cbf65710b889078558f8a (opens in a new tab)
- git.kernel.org/stable/c/c342fef95252c92c46531da676784c833806fd9a (opens in a new tab)
- git.kernel.org/stable/c/9b4cf60c6b739461c5b4ec9c52587da6b2608786 (opens in a new tab)