mm: avoid overflows in dirty throttling logic
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.19.320, 5.4.282, 5.10.222, 5.15.163, 6.1.98, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 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: mm: avoid overflows in dirty throttling logic The dirty throttling logic is interspersed with assumptions that dirty limits in PAGE_SIZE units fit into 32-bit (so that various multiplications fit into 64-bits). If limits end up being larger, we will hit overflows, possible divisions by 0 etc. Fix these problems by never allowing so large dirty limits as they have dubious practical value anyway. For dirty_bytes / dirty_background_bytes interfaces we can just refuse to set so large limits. For dirty_ratio / dirty_background_ratio it isn't so simple as the dirty limit is computed from the amount of available memory which can change due to memory hotplug etc. So when converting dirty limits from ratios to numbers of pages, we just don't allow the result to exceed UINT_MAX. This is root-only triggerable problem which occurs when the operator sets dirty limits to >16 TB.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 2da02997e08d3efe8174c7a47696e6f7cbe69ba9 · fixed in 2b2d2b8766db028bd827af34075f221ae9e9efff; From 2da02997e08d3efe8174c7a47696e6f7cbe69ba9 · fixed in 4d3817b64eda07491bdd86a234629fe0764fb42a; From 2da02997e08d3efe8174c7a47696e6f7cbe69ba9 · fixed in 7a49389771ae7666f4dc3426e2a4594bf23ae290; From 2da02997e08d3efe8174c7a47696e6f7cbe69ba9 · fixed in a25e8536184516b55ef89ab91dd2eea429de28d2; From 2da02997e08d3efe8174c7a47696e6f7cbe69ba9 · fixed in c83ed422c24f0d4b264f89291d4fabe285f80dbc; From 2da02997e08d3efe8174c7a47696e6f7cbe69ba9 · fixed in bd16a7ee339aef3ee4c90cb23902afb6af379ea0; From 2da02997e08d3efe8174c7a47696e6f7cbe69ba9 · fixed in 8e0b5e7f2895eccef5c2a0018b589266f90c4805; From 2da02997e08d3efe8174c7a47696e6f7cbe69ba9 · fixed in 385d838df280eba6c8680f9777bfa0d0bfe7e8b2
- Linux Linux
2.6.29
- KernelLinux
From 2.6.29 · fixed in 4.19.320; From 4.20.0 · fixed in 5.4.282; From 5.5.0 · fixed in 5.10.222; From 5.11.0 · fixed in 5.15.163; From 5.16.0 · fixed in 6.1.98; From 6.2.0 · fixed in 6.6.39; From 6.7.0 · fixed in 6.9.9
References 8
git.kernel.org
- stable/c/2b2d2b8766db028bd827af34075f221ae9e9efff
- stable/c/4d3817b64eda07491bdd86a234629fe0764fb42a
- stable/c/7a49389771ae7666f4dc3426e2a4594bf23ae290
- stable/c/a25e8536184516b55ef89ab91dd2eea429de28d2
- stable/c/c83ed422c24f0d4b264f89291d4fabe285f80dbc
- stable/c/bd16a7ee339aef3ee4c90cb23902afb6af379ea0
- stable/c/8e0b5e7f2895eccef5c2a0018b589266f90c4805
- stable/c/385d838df280eba6c8680f9777bfa0d0bfe7e8b2