CVE-2025-38084 is a race condition in the Linux kernel hugetlb memory-management subsystem during virtual memory area (VMA) splitting. The affected path caused __split_vma() to invoke hugetlb page-table unsharing via vm_ops->may_split() before acquiring the VMA and reverse-mapping locks. Concurrent VMA-locked page faults in the same process or reverse-mapping walks in other processes could consequently re-share page tables before the VMA split completed, defeating the intended protection. The fix invokes hugetlb unsharing within __split_vma() at the corresponding huge-page split stage, after the VMA and reverse-mapping locks are write-locked.
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.
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel mm/hugetlb flaw involving page-table unsharing during virtual memory area splitting.
A Linux kernel hugetlb memory-management issue involving page-table unsharing during a VMA split.
A Linux kernel hugetlb race condition in VMA splitting. Page-table unsharing was performed before required VMA and reverse-mapping locks were acquired, allowing concurrent operations to re-share page tables before the split. The fix moves unsharing into the appropriately write-locked split path.
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.