CVE-2025-37958 is a race condition in the Linux kernel mm/huge_memory subsystem. During transparent huge page migration, a concurrent deferred split scan can encounter a locked PMD migration entry in split_huge_pmd_locked. The vulnerable logic attempts to process the migration entry through the ordinary PMD-folio path, resulting in an invalid-address dereference and kernel page fault. The upstream correction detects PMD migration entries and returns early, avoiding unsafe conversion and target-folio validation on a locked migration entry.
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.
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel huge-memory management flaw caused by dereferencing an invalid PMD migration entry.
Linux kernel huge-memory management flaw caused by dereferencing an invalid PMD migration entry.
A Linux kernel huge-memory management flaw caused by dereferencing an invalid PMD migration entry.
A Linux kernel memory-management/huge-memory flaw caused by dereferencing an invalid PMD migration entry.
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.