CVE-2026-63807 is a flaw in the Linux kernel's KVM x86 shadow MMU hugepage recovery logic. The bug occurs because KVM queries the maximum mapping level for a shadow page's guest frame number before first verifying that the hugepage base guest frame number is actually contained within the target memslot. In the affected path, a guest can create a hugepage mapping whose range extends below the bounds of a memslot. KVM may then create a direct shadow page whose guest frame number lies outside the memslot even though the leaf reverse-mapping entry remains in bounds. During hugepage recovery, the kernel subsequently uses that out-of-bounds guest frame number when consulting memslot large-page metadata, leading to an out-of-bounds access to lpage_info. In typical cases this manifests as a host kernel page fault in kvm_mmu_max_mapping_level().
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.
1 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.