CVE-2026-72169

kho: make sure scratch size is always aligned by CMA_MIN_ALIGNMENT_BYTES

N/A
Published: August 15, 2026 at 05:53 AM UTC
Updated: August 17, 2026 at 06:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.16 ≤ v < 6.18.426.16 ≤ v < 7.1.56.16 ≤ v < 7.23dc92c311498c4d307cfdd0c6c3ac9355b50f6836.16
Vendor states this is fixed in 0e39380a7316122e1b00012b3f3cd3e318b3e7d3 (fixed)
Vendor states this is fixed in 9fefab759f59bf891bef7be15aee4bc7caec7ec3 (fixed)
Vendor states this is fixed in b8271be34bce151597da5b5179e0648c281322a4 (fixed)
Vendor states this is fixed in 6.16 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card