{"id":"CVE-2026-99699","summary":"mm/cma: accept memory of multi-range CMA areas","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/cma: accept memory of multi-range CMA areas\n\nPatch series \"mm/cma: accept memory of CMA areas reserved with\nmemblock_reserve()\", v1.\n\nPages of allocated CMA areas are released to the buddy allocator with\n__free_pages(), which does not check for unaccepted memory.\n\nThis usually works because memblock accepts the memory it allocates.\n\nHowever, multi-range CMA areas, used by hugetlb_cma, and fixed CMA areas\nrequested with cma=\u003csize\u003e@\u003cbase\u003e are reserved with memblock_reserve() and\ntheir memory is never accepted.\n\nOn TDX and SEV-SNP guests the first access to such a page is fatal.\n\nTo ease the backporting, each case is addressed by a separate patch:\n- patch 1 accepts the memory of multi-range CMA areas\n- patch 2 does the same for the fixed CMA areas\n\nThe second patch won't apply cleanly to 6.6 and 6.12, but I believe the\nstable team LLMs will take care of that :)\n\n\nThis patch (of 2):\n\nOn systems with unaccepted memory, memblock allocations accept the\nallocated range, but when cma_declare_contiguous_multi() uses open coded\nallocation of multiple ranges, it reserves them with memblock_reserve()\nand they are never accepted.\n\nThese pages are released to the buddy allocator by cma_activate_area()\nwith __free_pages() that does not check for unaccepted memory, so the\nfirst access to such a page in a TDX or SEV-SNP guest is fatal.\n\nAccept the memory of each range when it is reserved.","modified":"2026-11-20T07:01:09.826646239Z","published":"2026-11-20T05:50:41.851Z","database_specific":{"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99699.json","cna_assigner":"Linux"},"references":[{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"},{"type":"WEB","url":"https://git.kernel.org/stable/c/5d002001601a163b6c3500cdc098ff66c34f62d8"},{"type":"WEB","url":"https://git.kernel.org/stable/c/89b722ba00b0a6efd3ea14c1fc7996eb3b5a22c1"},{"type":"WEB","url":"https://git.kernel.org/stable/c/8e2dcdc9806546b4bda6f5904c96f1e5c20d477e"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99699.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99699"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"c009da4258f9885c5a3749fc004870db9c0e7a99"},{"fixed":"8e2dcdc9806546b4bda6f5904c96f1e5c20d477e"},{"fixed":"89b722ba00b0a6efd3ea14c1fc7996eb3b5a22c1"},{"fixed":"5d002001601a163b6c3500cdc098ff66c34f62d8"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99699.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.15.0"},{"fixed":"6.18.64"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.3.5"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99699.json"}}],"schema_version":"1.9.2"}