Loading vulnerability…
CVE-2024-42102 is an integer-overflow flaw in the Linux kernel mm/writeback dirty-throttling logic. A prior change to wb_dirty_limits() removed a 64-bit cast from a multiplication involving wb_thresh and bg_thresh. On 32-bit architectures, the multiplication can overflow when the product reaches or exceeds 2^32. The issue was addressed by reverting the faulty change as part of the dirty-throttling overflow fixes. The affected logic relies on dirty limits, expressed in page units, fitting within 32 bits.
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.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel vulnerability related to reverting a prior mm/writeback fix for wb_dirty_limits().
Linux kernel memory writeback flaw involving a possible divide-by-zero condition in wb_dirty_limits().
Linux kernel writeback issue related to a possible divide-by-zero condition in wb_dirty_limits().
A Linux kernel memory-management/writeback dirty-throttling flaw in which an incorrect change could cause multiplication overflow on 32-bit architectures when calculating dirty limits. The issue was resolved by reverting the faulty commit as part of a patch series intended to prevent dirty-throttling overflows.
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.