Quick answers
- Is CVE-2026-99286 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-99286 being exploited in the wild.
- How severe is CVE-2026-99286?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Linux Kernel multiple versions prior to fix.
- Is there a fix for CVE-2026-99286?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-99286 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-99286?
- Check whether you run Linux Kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a use-after-free race condition in xen-netback's xenbus.c where xenvif_get_stats and xenvif_get_ethtool_stats capture vif->num_queues under RCU read lock. The cleanup code must set vif->num_queues to zero before synchronize_net() to prevent readers from accessing deallocated queue structures. The fix reorders operations to unpublish the queue count prior to synchronization, matching the pattern used in backend_disconnect.
Affected products
- Linux Linux kernel multiple versions prior to fix
Timeline
- 2026-11-10: disclosed