CVE-2026-99699
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 memblock_reserve()", v1. Pages of allocated CMA areas are released to the buddy allocator with __free_pages(), which does not check for unaccepted memory. This usually works because memblock accepts the memory it allocates. However, multi-range CMA areas, used by hugetlb_cma, and fixed CMA areas requested with cma=<size>@<base> are reserved with memblock_reserve() 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 cma_declare_contiguous_multi() uses open coded allocation of multiple ranges, it reserves them with memblock_reserve() and they are never accepted. These pages are released to the buddy allocator by cma_activate_area() with __free_pages() 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.
Properties
- Last source
- FIRST EPSS
- Nvd fetched at
- 2026-11-22T12:30:49.958423+00:00
- Epss score
- 0.00166
- Cve id
- CVE-2026-99699
- First seen by Signal
- 2026-11-20T07:38:10+00:00
- Name
- CVE-2026-99699
- Retrieved at
- 2026-11-22T12:32:29+00:00
- Published at
- 2026-11-20T06:18:05.440
- Last modified
- 2026-11-20T06:18:05.440
- Epss percentile
- 0.05929
Related research
Explore deeper with Ninja Signal's threat intelligence graph