CVE-2024-26704 is a double-free vulnerability in the Linux kernel ext4 filesystem's ext4_move_extents() function. When moving extents partially succeeds but the operation subsequently fails, moved_len is not updated to reflect the extents already moved. Consequently, inode preallocations are not discarded. If moved extents overlap preallocated extents, ext4 can free the overlapping blocks twice through ext4_mb_release_inode_pa() and ext4_process_freed_data(), corrupting block-accounting state. A subsequent filesystem trim can trigger a divide-by-zero fault in mb_update_avg_fragment_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.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Double-free flaw in Linux kernel ext4 extent processing.
Double-free vulnerability in Linux kernel ext4 filesystem extent handling.
Linux kernel ext4 double-free vulnerability caused by incorrect extents moved_len handling.
Linux kernel ext4 double-free condition caused by an incorrect moved_len value.
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.