Loading vulnerability…
CVE-2024-39472 is an out-of-bounds access vulnerability in Linux kernel XFS log recovery. A legacy compatibility fixup corrects invalid h_size values in initial unmount log records produced by older xfsprogs versions. A subsequent cleanup of log-recovery buffer sizing stopped using the corrected h_size value when calculating the recovery-buffer allocation. Consequently, a malformed log record whose invalid h_size is not attributable to the legacy mkfs condition can cause recovery processing to access memory beyond the allocated buffer. The fix explicitly calculates the log-record header block count using the corrected h_size.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel XFS log-recovery buffer-allocation issue concerning the legacy h_size fixup.
Linux kernel XFS log-recovery buffer-allocation vulnerability.
A Linux kernel XFS log-recovery buffer-allocation vulnerability involving the legacy h_size fixup.
A Linux kernel XFS log-recovery buffer-allocation vulnerability involving the legacy h_size fixup.
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.