First published: Tue Jul 30 2024(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Linux kernel | <4.19.320 | |
Linux Linux kernel | >=4.20<5.4.282 | |
Linux Linux kernel | >=5.5<5.10.222 | |
Linux Linux kernel | >=5.11<5.15.163 | |
Linux Linux kernel | >=5.16<6.1.98 | |
Linux Linux kernel | >=6.2<6.6.39 | |
Linux Linux kernel | >=6.7<6.9.9 | |
Linux Linux kernel | =6.10-rc1 | |
Linux Linux kernel | =6.10-rc2 | |
Linux Linux kernel | =6.10-rc3 | |
Linux Linux kernel | =6.10-rc4 | |
Linux Linux kernel | =6.10-rc5 | |
Linux Linux kernel | =6.10-rc6 | |
redhat/kernel | <5.10.222 | 5.10.222 |
redhat/kernel | <5.15.163 | 5.15.163 |
redhat/kernel | <6.1.98 | 6.1.98 |
redhat/kernel | <6.6.39 | 6.6.39 |
redhat/kernel | <6.9.9 | 6.9.9 |
redhat/kernel | <6.10 | 6.10 |
debian/linux | 5.10.223-1 5.10.226-1 6.1.115-1 6.1.112-1 6.11.7-1 6.11.9-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.