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-99659: mm/mmu_gather: fix flushing ranges with 4 GiB or larger
Date: Fri, 20 Nov 2026 06:50:45 +0100	[thread overview]
Message-ID: <2026112047-CVE-2026-99659-55fb@gregkh> (raw)

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

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

mm/mmu_gather: fix flushing ranges with 4 GiB or larger

__tlb_adjust_range() takes the size of the range which has to be flushed
as an unsigned int. Its callers, tlb_flush_{pte,pmd,pud,p4d}_range(), get
and pass an unsigned long. Consequently, a range that is 4 GiB or larger
gets truncated, possibly to 0.

On arm64 with hugetlb, a 64k kernel can have 16 GiB hugetlb folios
mapped contiguously at the PMD level and flush them when unmapping, and a
16k kernel can flush 64 GiB PUDs through tlb_unshare_pmd_ptdesc(). So
at least these two scenarios are affected.

Fix it by flushing the proper range instead of the truncated one by
properly using "unsigned long" for range_size.

Fix generated by an LLM and sent by Josef Bacik in private.

[ david: use two-tab indent, simplify description ]

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


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

	Issue introduced in 4.10 with commit b528e4b6405b9fd656a6a308a7e2aa6afa50e77d and fixed in 6.12.118 with commit da895690b531ba3905c69bd2ed1c447dafa7b4ce
	Issue introduced in 4.10 with commit b528e4b6405b9fd656a6a308a7e2aa6afa50e77d and fixed in 6.18.64 with commit 2e12a0d8fa2ea4af9a74f414063359d965784919
	Issue introduced in 4.10 with commit b528e4b6405b9fd656a6a308a7e2aa6afa50e77d and fixed in 7.3.5 with commit 3647c49f164004458b5e767deed033bc13a25a2d
	Issue introduced in 4.10 with commit b528e4b6405b9fd656a6a308a7e2aa6afa50e77d and fixed in 7.4-rc2 with commit 64ae7959a1df8af8eec504e31df2ec9670424a4e

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-99659
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:
	include/asm-generic/tlb.h


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/da895690b531ba3905c69bd2ed1c447dafa7b4ce
	https://git.kernel.org/stable/c/2e12a0d8fa2ea4af9a74f414063359d965784919
	https://git.kernel.org/stable/c/3647c49f164004458b5e767deed033bc13a25a2d
	https://git.kernel.org/stable/c/64ae7959a1df8af8eec504e31df2ec9670424a4e

                 reply	other threads:[~2026-11-20  5:56 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=2026112047-CVE-2026-99659-55fb@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.