{"api_version":"1","generated_at":"2026-11-20T07:30:04+00:00","cve":"CVE-2026-99699","urls":{"html":"https://cve.report/CVE-2026-99699","api":"https://cve.report/api/cve/CVE-2026-99699.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-99699","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-99699"},"summary":{"title":"mm/cma: accept memory of multi-range CMA areas","description":"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=<size>@<base> 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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-11-20 06:18:05","updated_at":"2026-11-20 06:18:05"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/89b722ba00b0a6efd3ea14c1fc7996eb3b5a22c1","name":"https://git.kernel.org/stable/c/89b722ba00b0a6efd3ea14c1fc7996eb3b5a22c1","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/5d002001601a163b6c3500cdc098ff66c34f62d8","name":"https://git.kernel.org/stable/c/5d002001601a163b6c3500cdc098ff66c34f62d8","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/8e2dcdc9806546b4bda6f5904c96f1e5c20d477e","name":"https://git.kernel.org/stable/c/8e2dcdc9806546b4bda6f5904c96f1e5c20d477e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-99699","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99699","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected c009da4258f9885c5a3749fc004870db9c0e7a99 8e2dcdc9806546b4bda6f5904c96f1e5c20d477e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected c009da4258f9885c5a3749fc004870db9c0e7a99 89b722ba00b0a6efd3ea14c1fc7996eb3b5a22c1 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected c009da4258f9885c5a3749fc004870db9c0e7a99 5d002001601a163b6c3500cdc098ff66c34f62d8 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.15","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.15 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.64 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3.5 7.3.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.4-rc2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["mm/cma.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"8e2dcdc9806546b4bda6f5904c96f1e5c20d477e","status":"affected","version":"c009da4258f9885c5a3749fc004870db9c0e7a99","versionType":"git"},{"lessThan":"89b722ba00b0a6efd3ea14c1fc7996eb3b5a22c1","status":"affected","version":"c009da4258f9885c5a3749fc004870db9c0e7a99","versionType":"git"},{"lessThan":"5d002001601a163b6c3500cdc098ff66c34f62d8","status":"affected","version":"c009da4258f9885c5a3749fc004870db9c0e7a99","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["mm/cma.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.15"},{"lessThan":"6.15","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.64","versionType":"semver"},{"lessThanOrEqual":"7.3.*","status":"unaffected","version":"7.3.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.4-rc2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.64","versionStartIncluding":"6.15","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3.5","versionStartIncluding":"6.15","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.4-rc2","versionStartIncluding":"6.15","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"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=<size>@<base> 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."}],"providerMetadata":{"dateUpdated":"2026-11-20T05:50:41.851Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/8e2dcdc9806546b4bda6f5904c96f1e5c20d477e"},{"url":"https://git.kernel.org/stable/c/89b722ba00b0a6efd3ea14c1fc7996eb3b5a22c1"},{"url":"https://git.kernel.org/stable/c/5d002001601a163b6c3500cdc098ff66c34f62d8"}],"title":"mm/cma: accept memory of multi-range CMA areas","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-99699","datePublished":"2026-11-20T05:50:41.851Z","dateReserved":"2026-09-25T10:25:14.429Z","dateUpdated":"2026-11-20T05:50:41.851Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-20 06:18:05","lastModifiedDate":"2026-11-20 06:18:05","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"99699","Ordinal":"1","Title":"mm/cma: accept memory of multi-range CMA areas","CVE":"CVE-2026-99699","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"99699","Ordinal":"1","NoteData":"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=<size>@<base> 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.","Type":"Description","Title":"mm/cma: accept memory of multi-range CMA areas"}]}}}