Skip to main content
VulnerabilityPublished

CVE-2026-99699: Linux kernel · mm/cma: accept memory of multi-range CMA areas

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99699· High

Not known to be exploited · fixed in 89b722ba00b0a6efd3ea14c1fc7996eb3b5a22c1 : patch Linux kernel soon.

Data as of 20 Nov 2026, 07:34 UTC

Severity
High

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 89b722ba00b0a6efd3ea14c1fc7996eb3b5a22c1, 8e2dcdc9806546b4bda6f5904c96f1e5c20d477e, 5d002001601a163b6c3500cdc098ff66c34f62d8

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Linux kernel to 89b722ba00b0a6efd3ea14c1fc7996eb3b5a22c1, 8e2dcdc9806546b4bda6f5904c96f1e5c20d477e or 5d002001601a163b6c3500cdc098ff66c34f62d8.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ c009da4258f9885c5a3749fc004870db9c0e7a99, < 89b722ba00b0a6efd3ea14c1fc7996eb3b5a22c1
Fixed in
  • 89b722ba00b0a6efd3ea14c1fc7996eb3b5a22c1
LinuxLinuxAffected
  • ≥ c009da4258f9885c5a3749fc004870db9c0e7a99, < 8e2dcdc9806546b4bda6f5904c96f1e5c20d477e
Fixed in
  • 8e2dcdc9806546b4bda6f5904c96f1e5c20d477e
LinuxLinuxAffected
  • ≥ c009da4258f9885c5a3749fc004870db9c0e7a99, < 5d002001601a163b6c3500cdc098ff66c34f62d8
Fixed in
  • 5d002001601a163b6c3500cdc098ff66c34f62d8
LinuxLinuxAffected
  • =6.15
Fixed in–

Description

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.

References

Community reviews

Loading reviews…