Loading vulnerability…
CVE-2024-26601 is an ext4 filesystem metadata-corruption flaw in Linux kernel fast-commit replay. During replay, block-freeing logic can encounter blocks that are already recorded as free. The resulting failed free operation can leave ext4 buddy allocator metadata inconsistent because the buddy bitmap is not regenerated. The upstream regression was introduced in Linux kernel 5.11; the correction restores buddy metadata regeneration after a failed block-free operation during fast-commit replay and was merged upstream in Linux kernel 6.8.
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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel ext4 fast-commit replay handling issue after failed block freeing.
Linux kernel ext4 filesystem flaw involving buddy regeneration following block-freeing failure during fast-commit replay.
Linux kernel ext4 filesystem flaw involving buddy regeneration after failed block freeing during fast-commit replay.
A vulnerability remediated by the OpenShift Container Platform 4.14.35 security update; no technical description is provided.
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.