All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99698: mm/cma: accept memory of CMA areas reserved at a fixed address
Date: Fri, 20 Nov 2026 06:51:24 +0100	[thread overview]
Message-ID: <2026112001-CVE-2026-99698-623a@gregkh> (raw)

From: Greg Kroah-Hartman <gregkh@kernel.org>

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.

The Linux kernel CVE team has assigned CVE-2026-99698 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.5 with commit 75d090fd167acab4d7eda7e2b65729e877c0fd64 and fixed in 6.18.64 with commit 6b1e545759608795f8c6123cca892073a5e5a38d
	Issue introduced in 6.5 with commit 75d090fd167acab4d7eda7e2b65729e877c0fd64 and fixed in 7.3.5 with commit 167d6b31a447902c205b34638a6c90b55253f216
	Issue introduced in 6.5 with commit 75d090fd167acab4d7eda7e2b65729e877c0fd64 and fixed in 7.4-rc2 with commit f8f9cbc34a309a388c052706f3329d1b52985aa3

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2026-99698
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	mm/cma.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/6b1e545759608795f8c6123cca892073a5e5a38d
	https://git.kernel.org/stable/c/167d6b31a447902c205b34638a6c90b55253f216
	https://git.kernel.org/stable/c/f8f9cbc34a309a388c052706f3329d1b52985aa3

                 reply	other threads:[~2026-11-20  5:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2026112001-CVE-2026-99698-623a@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cve@kernel.org \
    --cc=gregkh@kernel.org \
    --cc=linux-cve-announce@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.