Answer in brief
CVE-2024-42131 records a Unknown severity vulnerability in mm: avoid overflows in dirty throttling logic. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/RUGGEDCOM RST2428P (generic), Siemens/SCALANCE XCM-/XRM-/XCH-/XRH-300 family (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/RUGGEDCOM RST2428P (generic), Siemens/SCALANCE XCM-/XRM-/XCH-/XRH-300 family (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2da02997e08d3efe8174c7a47696e6f7cbe69ba9 <2b2d2b8766db028bd827af34075f221ae9e9efff || >=2da02997e08d3efe8174c7a47696e6f7cbe69ba9 <4d3817b64eda07491bdd86a234629fe0764fb42a || >=2da02997e08d3efe8174c7a47696e6f7cbe69ba9 <7a49389771ae7666f4dc3426e2a4594bf23ae290 || >=2da02997e08d3efe8174c7a47696e6f7cbe69ba9 <a25e8536184516b55ef89ab91dd2eea429de28d2 || >=2da02997e08d3efe8174c7a47696e6f7cbe69ba9 <c83ed422c24f0d4b264f89291d4fabe285f80dbc || >=2da02997e08d3efe8174c7a47696e6f7cbe69ba9 <bd16a7ee339aef3ee4c90cb23902afb6af379ea0 || >=2da02997e08d3efe8174c7a47696e6f7cbe69ba9 <8e0b5e7f2895eccef5c2a0018b589266f90c4805 || >=2da02997e08d3efe8174c7a47696e6f7cbe69ba9 <385d838df280eba6c8680f9777bfa0d0bfe7e8b2 | 2b2d2b8766db028bd827af34075f221ae9e9efff, 4d3817b64eda07491bdd86a234629fe0764fb42a, 7a49389771ae7666f4dc3426e2a4594bf23ae290, a25e8536184516b55ef89ab91dd2eea429de28d2, c83ed422c24f0d4b264f89291d4fabe285f80dbc, bd16a7ee339aef3ee4c90cb23902afb6af379ea0, 8e0b5e7f2895eccef5c2a0018b589266f90c4805, 385d838df280eba6c8680f9777bfa0d0bfe7e8b2 |
| Linux/Linuxgeneric | 2.6.29 | Not reported |
| Siemens/RUGGEDCOM RST2428Pgeneric | >=0 <V3.1 | V3.1 |
| Siemens/SCALANCE XCM-/XRM-/XCH-/XRH-300 familygeneric | >=0 <V3.1 | V3.1 |
| Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.0 <V3.1.5 | V3.1.5 |
| Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric | >=V3.1.0 <V3.1.5 | V3.1.5 |
| Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.0 <V3.1.5 | V3.1.5 |
Published upstream
Jul 30, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.