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

Published Nov 20, 2026
·
Updated

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 memblockallocrangenid(), but areas reserved at a fixed address with memblockreserve() 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.

Affected Software

5 affected componentsFixes available
linux/kernel>=6.5.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5
debian/linux*
debian/linux*
debian/linux<=6.12.107-1, <=6.12.117-1, <=7.3.4-1
6.1.176-16.1.192-27.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  3. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 7.3.5-1

Event History

Nov 20, 2026
CVE Published
via MITRE·05:50 AM
Data Sourced
via MITRE·05:50 AM
Description
Data Sourced
via OSV·05:50 AM
DescriptionAffected Software
Data Sourced
via NVD·06:18 AM
Description

Frequently Asked Questions

1

Which systems are exposed to this issue?

The issue affects Linux kernel guests using TDX or SEV-SNP when a CMA area is explicitly reserved at a fixed address with the cma=<size>@<base> kernel command-line parameter and that region is regular RAM.

2

What configuration is required for the problem to occur?

A fixed-address CMA area must be requested through cma=<size>@<base>. CMA areas allocated through memblock_alloc_range_nid() already have their memory accepted, so the described gap applies to areas reserved with memblock_reserve().

3

How can I determine whether a system may be affected?

Check the kernel command line for a cma=<size>@<base> parameter. Systems without a fixed-base CMA reservation are not described as affected by this issue.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203