A race condition in Xen grant-table version switching affects the transition from grant table version 2 back to version 1. The flaw arises because code handling grant tables may drop and later re-acquire the grant table lock while incorrectly assuming that grant-table properties remain unchanged during the unlocked interval. In the v2-to-v1 case, this assumption is invalid because the separate status frames used by grant table v2 disappear when switching back to v1. As a result, concurrent operations can observe or act on stale assumptions about grant-table layout and state, leading to incorrect grant-table handling and potential security boundary violations in the hypervisor.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.