CVE-2026-99698: mm/cma: accept memory of CMA areas reserved at a fixed address
In the Linux kernel, the following vulnerability has been resolved:
mm/cma: accept memory of CMA areas reserved at a fixed address
CMA areas allocated from memblock have their memory accepted by memblockallocrangenid(), but areas reserved at a fixed address with memblockreserve() are not.
If a fixed CMA area is requested by the cma=<size>@<base> command line parameter, it may be in regular RAM and on TDX and SEV-SNP guests it must be accepted.
Accept the memory of fixed CMA areas as well, so that all CMA areas are accepted regardless of how they were reserved.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 7.3.5-1
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
The issue affects Linux kernel guests using TDX or SEV-SNP when a CMA area is explicitly reserved at a fixed address with the cma=<size>@<base> kernel command-line parameter and that region is regular RAM.
What configuration is required for the problem to occur?
A fixed-address CMA area must be requested through cma=<size>@<base>. CMA areas allocated through memblock_alloc_range_nid() already have their memory accepted, so the described gap applies to areas reserved with memblock_reserve().
How can I determine whether a system may be affected?
Check the kernel command line for a cma=<size>@<base> parameter. Systems without a fixed-base CMA reservation are not described as affected by this issue.