CVE-2024-26773 is a vulnerability in the Linux kernel ext4 filesystem allocator's ext4_mb_try_best_found() function. The allocator checks a block group's bitmap and selects an extent while holding the group lock, then releases the lock before using the selected extent. If the bitmap is marked corrupted during this interval, ext4_mb_try_best_found() can subsequently allocate blocks from the corrupted group because it does not recheck the corruption state. This can worsen filesystem corruption and potentially cause system crashes.
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.
A medium-severity Linux kernel ext4 filesystem flaw in the multiblock allocator. A race condition can allow allocation from a block group after its block bitmap has been marked corrupted, affecting availability through further filesystem corruption.
A Linux kernel ext4 flaw involving allocation of blocks from a corrupted group in ext4_mb_try_best_found(). Listed as fixed by the updated container image.
Linux kernel ext4 flaw allowing block allocation from a corrupted block group.
Linux kernel ext4 allocation flaw involving corrupted block groups.
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.