Loading vulnerability…
CVE-2026-23097 is an incorrect lock-ordering vulnerability in the Linux kernel migration subsystem affecting file-backed hugetlb folios. During hugetlb page migration, the unmap-and-move path acquires folio_lock and subsequently attempts to acquire i_mmap_rwsem through remove_migration_ptes() and reverse-map walking. Concurrent hugetlbfs fallocate or hole-punch processing acquires i_mmap_rwsem for writing and subsequently waits for folio_lock. This lock inversion produces an ABBA deadlock. The fix extends the existing i_mmap lock scope to include remove_migration_ptes() for file-backed hugetlb pages, restoring the required lock ordering.
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.
30 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel denial-of-service vulnerability caused by a deadlock in hugetlb folio migration.
A Linux kernel denial-of-service vulnerability caused by a deadlock in hugetlb folio migration.
A Linux kernel denial-of-service vulnerability caused by a deadlock in hugetlb folio migration.
A Linux kernel denial-of-service vulnerability caused by a deadlock in hugetlb folio migration.
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.