Skip to main content
cve.nowby Sazabi
← All vulnerabilities
CVE-2024-42102

Revert "mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again"

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 4.19.318, 5.4.280, 5.10.222, 5.15.163, 6.1.98, and 2 more
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

In the Linux kernel, the following vulnerability has been resolved: Revert "mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again" Patch series "mm: Avoid possible overflows in dirty throttling". Dirty throttling logic assumes dirty limits in page units fit into 32-bits. This patch series makes sure this is true (see patch 2/2 for more details). This patch (of 2): This reverts commit 9319b647902cbd5cc884ac08a8a6d54ce111fc78. The commit is broken in several ways. Firstly, the removed (u64) cast from the multiplication will introduce a multiplication overflow on 32-bit archs if wb_thresh * bg_thresh >= 1<<32 (which is actually common - the default settings with 4GB of RAM will trigger this). Secondly, the div64_u64() is unnecessarily expensive on 32-bit archs. We have div64_ul() in case we want to be safe & cheap. Thirdly, if dirty thresholds are larger than 1<<32 pages, then dirty balancing is going to blow up in many other spectacular ways anyway so trying to fix one possible overflow is just moot.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  3. Record last updated

Affected versions

  • Linux Linux

    From 4.19.307 · fixed in 4.19.318; From 5.4.269 · fixed in 5.4.280; From 5.10.210 · fixed in 5.10.222; From 5.15.149 · fixed in 5.15.163; From 6.1.79 · fixed in 6.1.98; From 6.6.18 · fixed in 6.6.39; From 6.7.6 · fixed in 6.8

  • Linux Linux

    6.8

References 8

git.kernel.org