Loading vulnerability…
CVE-2024-26720 has been rejected by its CVE Numbering Authority. It was originally assigned to a potential divide-by-zero condition in the Linux kernel memory-management writeback path, in wb_dirty_limits(). On platforms where unsigned long is wider than 32 bits, a full-width dirty-threshold value was passed to div_u64(), whose divisor parameter is 32-bit. A threshold equal to 2^32 could therefore be truncated to zero before division. Upstream corrected the width mismatch by using div64_u64() for the relevant calculation.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel vulnerability in mm/writeback that can cause a divide-by-zero in wb_dirty_limits().
Linux kernel writeback divide-by-zero flaw.
Linux kernel memory writeback divide-by-zero flaw in wb_dirty_limits().
A possible divide-by-zero flaw in the Linux kernel writeback dirty-limit calculation.
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.