Loading vulnerability…
CVE-2026-31787 is a Linux kernel memory-management flaw in the Xen privcmd driver, also tracked as XSA-487. The bug arises because privcmd_vm_ops implements a .close handler, privcmd_close, but does not implement .may_split or .open. When userspace performs a partial munmap() on a privcmd mapping, the kernel may split the VMA through __split_vma(). Because splitting is permitted and vm_area_dup() duplicates vm_private_data without any fixup, both resulting VMAs can reference the same pages array allocated by alloc_empty_pages(). When one VMA is closed, privcmd_close unmaps the range, frees the unpopulated pages, and releases the shared pages array. The remaining VMA retains a dangling pointer and later executes the same cleanup path again when destroyed, resulting in a double free of kernel memory.
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.
27 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel vulnerability in xen/privcmd involving a double free via VMA splitting.
A Linux kernel vulnerability in xen/privcmd involving a double free via VMA splitting.
A Linux kernel xen/privcmd double-free vulnerability triggered via VMA splitting.
A Linux kernel xen/privcmd double-free vulnerability triggered via VMA splitting.
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.