Skip to main content
VulnerabilityPublished

CVE-2026-99698: Linux kernel · mm/cma: accept memory of CMA areas reserved at a fixed address

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99698

Not known to be exploited · fixed in f8f9cbc34a309a388c052706f3329d1b52985aa3 : update Linux kernel when convenient.

Data as of 20 Nov 2026, 07:34 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in f8f9cbc34a309a388c052706f3329d1b52985aa3, 167d6b31a447902c205b34638a6c90b55253f216, 6b1e545759608795f8c6123cca892073a5e5a38d

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 f8f9cbc34a309a388c052706f3329d1b52985aa3, 167d6b31a447902c205b34638a6c90b55253f216 or 6b1e545759608795f8c6123cca892073a5e5a38d.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 75d090fd167acab4d7eda7e2b65729e877c0fd64, < f8f9cbc34a309a388c052706f3329d1b52985aa3
Fixed in
  • f8f9cbc34a309a388c052706f3329d1b52985aa3
LinuxLinuxAffected
  • ≥ 75d090fd167acab4d7eda7e2b65729e877c0fd64, < 167d6b31a447902c205b34638a6c90b55253f216
Fixed in
  • 167d6b31a447902c205b34638a6c90b55253f216
LinuxLinuxAffected
  • ≥ 75d090fd167acab4d7eda7e2b65729e877c0fd64, < 6b1e545759608795f8c6123cca892073a5e5a38d
Fixed in
  • 6b1e545759608795f8c6123cca892073a5e5a38d
LinuxLinuxAffected
  • =6.5
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: mm/cma: accept memory of CMA areas reserved at a fixed address CMA areas allocated from memblock have their memory accepted by memblock_alloc_range_nid(), but areas reserved at a fixed address with memblock_reserve() are not. If a fixed CMA area is requested by the cma=<size>@<base> command line parameter, it may be in regular RAM and on TDX and SEV-SNP guests it must be accepted. Accept the memory of fixed CMA areas as well, so that all CMA areas are accepted regardless of how they were reserved.

References

Community reviews

Loading reviews…