mm: avoid overflows in dirty throttling logic
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2da02997e08d3efe8174c7a47696e6f7cbe69ba9 · < bd16a7ee339aef3ee4c90cb23902afb6af379ea0| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's dirty throttling logic can overflow or divide by zero when dirty limits exceed 16 TB. Triggering the issue requires root privileges to set those limits; it is not described as a remote or user-interaction attack.
Operators running the Linux kernel should check systems where root may set dirty limits above 16 TB; affected versions were not specified.