CVE-2024-42131
Linux Kernel Dirty Throttling Overflow Vulnerability
Description
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.
INFO
Published Date :
July 30, 2024, 8:15 a.m.
Last Modified :
Sept. 25, 2024, 2:45 p.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
3.6
Exploitability Score :
0.8
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-42131.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-42131 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-42131 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Reanalysis by [email protected]
Sep. 25, 2024
Action Type Old Value New Value Removed CVSS V3.1 NIST AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Added CVSS V3.1 NIST AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H -
Initial Analysis by [email protected]
Sep. 16, 2024
Action Type Old Value New Value Added CVSS V3.1 NIST AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Changed Reference Type https://git.kernel.org/stable/c/2b2d2b8766db028bd827af34075f221ae9e9efff No Types Assigned https://git.kernel.org/stable/c/2b2d2b8766db028bd827af34075f221ae9e9efff Patch Changed Reference Type https://git.kernel.org/stable/c/385d838df280eba6c8680f9777bfa0d0bfe7e8b2 No Types Assigned https://git.kernel.org/stable/c/385d838df280eba6c8680f9777bfa0d0bfe7e8b2 Patch Changed Reference Type https://git.kernel.org/stable/c/4d3817b64eda07491bdd86a234629fe0764fb42a No Types Assigned https://git.kernel.org/stable/c/4d3817b64eda07491bdd86a234629fe0764fb42a Patch Changed Reference Type https://git.kernel.org/stable/c/7a49389771ae7666f4dc3426e2a4594bf23ae290 No Types Assigned https://git.kernel.org/stable/c/7a49389771ae7666f4dc3426e2a4594bf23ae290 Patch Changed Reference Type https://git.kernel.org/stable/c/8e0b5e7f2895eccef5c2a0018b589266f90c4805 No Types Assigned https://git.kernel.org/stable/c/8e0b5e7f2895eccef5c2a0018b589266f90c4805 Patch Changed Reference Type https://git.kernel.org/stable/c/a25e8536184516b55ef89ab91dd2eea429de28d2 No Types Assigned https://git.kernel.org/stable/c/a25e8536184516b55ef89ab91dd2eea429de28d2 Patch Changed Reference Type https://git.kernel.org/stable/c/bd16a7ee339aef3ee4c90cb23902afb6af379ea0 No Types Assigned https://git.kernel.org/stable/c/bd16a7ee339aef3ee4c90cb23902afb6af379ea0 Patch Changed Reference Type https://git.kernel.org/stable/c/c83ed422c24f0d4b264f89291d4fabe285f80dbc No Types Assigned https://git.kernel.org/stable/c/c83ed422c24f0d4b264f89291d4fabe285f80dbc Patch Added CWE NIST CWE-190 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions up to (excluding) 4.19.320 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.20 up to (excluding) 5.4.282 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.5 up to (excluding) 5.10.222 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.163 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.98 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.39 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.9.9 *cpe:2.3:o:linux:linux_kernel:6.10:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.10:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.10:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.10:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.10:rc5:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.10:rc6:*:*:*:*:*:* -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Aug. 19, 2024
Action Type Old Value New Value Added Reference kernel.org https://git.kernel.org/stable/c/2b2d2b8766db028bd827af34075f221ae9e9efff [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/4d3817b64eda07491bdd86a234629fe0764fb42a [No types assigned] -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 30, 2024
Action Type Old Value New Value Added Description 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. Added Reference kernel.org https://git.kernel.org/stable/c/7a49389771ae7666f4dc3426e2a4594bf23ae290 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/a25e8536184516b55ef89ab91dd2eea429de28d2 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/c83ed422c24f0d4b264f89291d4fabe285f80dbc [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/bd16a7ee339aef3ee4c90cb23902afb6af379ea0 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/8e0b5e7f2895eccef5c2a0018b589266f90c4805 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/385d838df280eba6c8680f9777bfa0d0bfe7e8b2 [No types assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-42131 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-42131
weaknesses.