CVE-2024-42131

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> mm: avoid overflows in dirty throttling logic<br /> <br /> The dirty throttling logic is interspersed with assumptions that dirty<br /> limits in PAGE_SIZE units fit into 32-bit (so that various multiplications<br /> fit into 64-bits). If limits end up being larger, we will hit overflows,<br /> possible divisions by 0 etc. Fix these problems by never allowing so<br /> large dirty limits as they have dubious practical value anyway. For<br /> dirty_bytes / dirty_background_bytes interfaces we can just refuse to set<br /> so large limits. For dirty_ratio / dirty_background_ratio it isn&amp;#39;t so<br /> simple as the dirty limit is computed from the amount of available memory<br /> which can change due to memory hotplug etc. So when converting dirty<br /> limits from ratios to numbers of pages, we just don&amp;#39;t allow the result to<br /> exceed UINT_MAX.<br /> <br /> This is root-only triggerable problem which occurs when the operator<br /> sets dirty limits to &gt;16 TB.