CVE-2024-26630 is a use-after-free vulnerability in the Linux kernel mm:cachestat cache-walk implementation. The code obtained a folio from the page-cache xarray and accessed its page offset plus dirty and writeback state without first retaining a folio reference. Concurrent reclamation could therefore free and reuse the folio as another folio, page, or slab object while cachestat was reading it. The upstream fix avoids dereferencing the folio for these values and instead uses xarray mechanisms to obtain page offsets and dirty/writeback state.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel memory-management vulnerability in cachestat causing a folio read-after-free during cache walk.
A Linux kernel memory-management (mm) vulnerability in cachestat cache walking that can result in a folio read-after-free. The issue was resolved upstream and subsequently fixed in Fedora kernel 6.7.9 stable updates and Red Hat Enterprise Linux 9.
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.