kho: make sure scratch size is always aligned by CMA_MIN_ALIGNMENT_BYTES
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0e39380a7316122e1b00012b3f3cd3e318b3e7d3, Kernel 9fefab759f59bf891bef7be15aee4bc7caec7ec3 and Kernel b8271be34bce151597da5b5179e0648c281322a4.
In the Linux kernel, the following vulnerability has been resolved: kho: make sure scratch size is always aligned by CMA_MIN_ALIGNMENT_BYTES When using scratch_scale, the scratch sizes are rounded up to CMA_MIN_ALIGNMENT_BYTES since they will be released as MIGRATE_CMA. This is not done when using fixed scratch sizes via command line. This can result in user specifying a size which is not aligned, and thus kernel releasing a pageblock that is only partially scratch. Do the rounding up for both cases in scratch_size_update().
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.16, >=3dc92c311498c4d307cfdd0c6c3ac9355b50f683 <0e39380a7316122e1b00012b3f3cd3e318b3e7d3, >=3dc92c311498c4d307cfdd0c6c3ac9355b50f683 <9fefab759f59bf891bef7be15aee4bc7caec7ec3, >=3dc92c311498c4d307cfdd0c6c3ac9355b50f683 <b8271be34bce151597da5b5179e0648c281322a4 | 0e39380a7316122e1b00012b3f3cd3e318b3e7d3, 9fefab759f59bf891bef7be15aee4bc7caec7ec3, b8271be34bce151597da5b5179e0648c281322a4 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket