Loading vulnerability…
CVE-2024-39472 is a buffer-sizing vulnerability in Linux kernel XFS log recovery. XFS corrects invalid h_size values associated with initial unmount records created by older xfsprogs versions. A subsequent regression in log-record header-block calculation stopped using the corrected h_size to allocate the recovery buffer. Malformed header-size values outside the legacy formatting scenario can consequently trigger out-of-bounds memory access. The fix replaces the xlog_logrec_hblks calculation with an inline calculation that accounts for 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.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel XFS log-recovery buffer-allocation flaw.
A medium-severity Linux kernel XFS filesystem vulnerability in log recovery. Incorrect handling of a malformed h_size field can cause an out-of-bounds access during recovery-buffer allocation.
Linux kernel XFS log-recovery buffer-allocation issue concerning the legacy h_size fixup.
Linux kernel XFS log-recovery buffer-allocation vulnerability.
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.