CVE-2024-41031 is a Linux kernel memory-management flaw in mm/filemap related to creation of PMD-sized page cache entries. On ARM64 systems using a 64 KB base page size, HPAGE_PMD_ORDER is 13, which can make the PMD-sized page cache larger than MAX_PAGECACHE_ORDER. In that configuration, the kernel may incorrectly attempt to create a PMD-sized page cache entry that cannot be supported by xarray, leading to a warning in xas_split_alloc() during page splitting and truncation paths. The provided trace shows the issue being reachable via fallocate on XFS, through xfs_file_fallocate() -> truncate_pagecache_range() -> truncate_inode_pages_range() -> truncate_inode_partial_folio() -> split_huge_page_to_list_to_order() -> xas_split_alloc(). The fix is to skip allocation of PMD-sized page cache when its size exceeds MAX_PAGECACHE_ORDER and fall back to the regular readahead/page-cache path.
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.
6 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.