CVE-2024-40972 is a Linux kernel ext4 locking flaw in extended-attribute handling. The ext4_xattr_set_entry() path could create a new extended-attribute (EA) inode while holding the buffer lock for an external xattr block. EA-inode creation performs allocation operations that can acquire locks on other buffers, resulting in unsafe lock nesting beneath the existing buffer lock. On a corrupted filesystem, including a condition in which a quota file references an xattr block as a data block, this lock ordering can deadlock. The upstream fix relocates EA-inode allocation from ext4_xattr_set_entry() to its callers, before the relevant buffer lock is held.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel ext4 extended-attribute inode creation issue involving a buffer lock.
Linux kernel ext4 extended-attribute inode creation under a buffer lock vulnerability.
A Linux kernel ext4 filesystem vulnerability in which creation of extended-attribute (EA) inodes occurred while holding an external xattr-buffer lock. Nested allocation locking under that lock can cause a deadlock, including in filesystem-corruption scenarios involving a quota file containing an xattr block as a data block.
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.