CVE-2026-99287: Linux kernel · xen-netback: Zero out sring pointers on unmap
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e7ba61734d6ad6adfd5bf617052e590743211669 : update Linux kernel when convenient.
Data as of 10 Nov 2026, 18:36 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in e7ba61734d6ad6adfd5bf617052e590743211669, c5f54af611ff6fe1d53fa05d8e87b469dc56122b, 87fd475dc4e354088f6534285388e7b061f54b35
Exploitation evidence
Disclosed: evidence found.
CVE published 10 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 10 Nov 2026.
What to do
Upgrade Linux kernel to e7ba61734d6ad6adfd5bf617052e590743211669, c5f54af611ff6fe1d53fa05d8e87b469dc56122b or 87fd475dc4e354088f6534285388e7b061f54b35.
Affected software
| Product | 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 as indicated by the fixed commit hashes. Users should update their Linux kernel to a version that includes these fixes to mitigate the vulnerability. No additional mitigation is required beyond applying the official patch.
Description
A vulnerability in the Linux kernel's xen-netback component involves improper handling of ring pointers during unmap operations. Specifically, when xenvif_map_frontend_data_rings() fails with rings already mapped, the ring pointers are not zeroed out after unmapping, leading to potential double unmap attempts. This issue has been fixed by zeroing out the ring pointers after unmapping to prevent repeated unmap calls. The fix is identified as XSA-532.