VDB

CVE-2024-42131

CVE-2024-42131 PUBLISHED

mm: avoid overflows in dirty throttling logic

Reported by linux · Published July 30, 2024

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
kernel-develAmazon Linux4.14.353-270.569.amzn2
LinuxLinuxc83ed422c24f0d4b264f89291d4fabe285f80dbc, bd16a7ee339aef3ee4c90cb23902afb6af379ea0, a25e8536184516b55ef89ab91dd2eea429de28d2, 8e0b5e7f2895eccef5c2a0018b589266f90c4805, 7a49389771ae7666f4dc3426e2a4594bf23ae290, 4d3817b64eda07491bdd86a234629fe0764fb42a, 385d838df280eba6c8680f9777bfa0d0bfe7e8b2, 2b2d2b8766db028bd827af34075f221ae9e9efff, 2.6.29

Affected products

VendorProductVersions
LinuxLinux2da02997e08d3efe8174c7a47696e6f7cbe69ba9, 2da02997e08d3efe8174c7a47696e6f7cbe69ba9, 2da02997e08d3efe8174c7a47696e6f7cbe69ba9
LinuxLinux2.6.29, 0, 4.19.320
amazon:2kernel-devel0
LinuxLinux2da02997e08d3efe8174c7a47696e6f7cbe69ba9, 2da02997e08d3efe8174c7a47696e6f7cbe69ba9, 6.6.39
linuxlinux_kernel2.6.29, 2.6.29, 2.6.29
amazon:2023kernel-headers0
amazon:2python-perf0
amazon:2023kernel0
amazon:2023perf0
amazon:2023kernel-tools0
amazon:2kernel-livepatch-4.14.353-270.5690
amazon:2023kernel-libbpf-devel0
amazon:2023kernel-libbpf0
amazon:2023kernel-modules-extra-common0
amazon:2kernel-tools0
amazon:2023kernel-tools-devel0
amazon:2kernel0
SiemensSCALANCE XCM-/XRM-/XCH-/XRH-300 family0
SiemensSIMATIC S7-1500 CPU 1518F-4 PN/DP MFP3.1.0
amazon:2023kernel-livepatch-6.1.102-108.1770

…and 12 more

Timeline

  • Jul 29, 2024 CVE Published
  • Jul 30, 2024 EPSS Score (30 in total, the first dated here)
  • Oct 4, 2024 Coalition ESS Score (9 in total, the first dated here)
  • Dec 16, 2025 PoC Published
  • Jan 6, 2026 Security Advisory (359 in total, the first dated here)
  • Mar 30, 2026 Distribution Patch (241 in total, the first dated here)
  • Nov 19, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2024-42131
vulnetix vdb fixes CVE-2024-42131

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-42131/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›