CVE-2026-99699: mm/cma: accept memory of multi-range CMA areas
In the Linux kernel, the following vulnerability has been resolved:
mm/cma: accept memory of multi-range CMA areas
Patch series "mm/cma: accept memory of CMA areas reserved with memblockreserve()", v1.
Pages of allocated CMA areas are released to the buddy allocator with freepages(), which does not check for unaccepted memory.
This usually works because memblock accepts the memory it allocates.
However, multi-range CMA areas, used by hugetlbcma, and fixed CMA areas requested with cma=<size>@<base> are reserved with memblockreserve() and their memory is never accepted.
On TDX and SEV-SNP guests the first access to such a page is fatal.
To ease the backporting, each case is addressed by a separate patch: - patch 1 accepts the memory of multi-range CMA areas - patch 2 does the same for the fixed CMA areas
The second patch won't apply cleanly to 6.6 and 6.12, but I believe the stable team LLMs will take care of that :)
This patch (of 2):
On systems with unaccepted memory, memblock allocations accept the allocated range, but when cmadeclarecontiguousmulti() uses open coded allocation of multiple ranges, it reserves them with memblockreserve() and they are never accepted.
These pages are released to the buddy allocator by cmaactivatearea() with freepages() that does not check for unaccepted memory, so the first access to such a page in a TDX or SEV-SNP guest is fatal.
Accept the memory of each range when it is 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 6.12.107-1Fixed in 6.12.117-1Fixed in 7.3.5-1
Event History
Frequently Asked Questions
Which systems are exposed to the fatal failure described here?
The issue affects systems with unaccepted memory, specifically TDX and SEV-SNP guests. The failure occurs when such a guest first accesses a page from an affected CMA area.
What CMA configurations can create unaccepted pages?
Multi-range CMA areas declared through cma_declare_contiguous_multi() are affected because their ranges are reserved with memblock_reserve() rather than accepted through a memblock allocation. These multi-range areas are used by hugetlb_cma.
Does this change also cover fixed CMA areas configured with cma=<size>@<base>?
No. The provided patch is the first of two and addresses multi-range CMA areas. Fixed CMA areas requested with cma=<size>@<base> require the separate second patch described in the patch series.