All of lore.kernel.org
 help / color / mirror / Atom feed
* CVE-2026-99703: mm/hugetlb: fix mremap deadlock when PMD sharing is possible
@ 2026-11-20  5:51 Greg Kroah-Hartman
  0 siblings, 0 replies; only message in thread
From: Greg Kroah-Hartman @ 2026-11-20  5:51 UTC (permalink / raw)
  To: linux-cve-announce; +Cc: Greg Kroah-Hartman

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

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

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

mm/hugetlb: fix mremap deadlock when PMD sharing is possible

move_hugetlb_page_tables() holds the mapping's i_mmap_rwsem for
write while moving hugetlb PTEs. This prevents races with truncation
and protects huge_pmd_unshare(), but the move loop must not call
helpers that can acquire the same rwsem for read.

huge_pte_alloc() can do that when the destination can use PMD
sharing: it may call huge_pmd_share(), which takes i_mmap_rwsem for
read while searching for a shareable PMD table. Calling it while the
move path already holds i_mmap_rwsem for write can deadlock.

Avoid that path for PMD-sized hugetlb mappings that can use PMD
sharing. Instead of allocating or sharing the destination page table
while moving, zap the source range and let the destination fault path
populate or share the PMD lazily.

Reuse the hugetlb unmap logic for the source-side zap by splitting
the core loop out of __unmap_hugepage_range(). The wrapper keeps the
existing tlb_start_vma(), tlb_end_vma() and huge_pmd_unshare_flush()
behavior, while move_hugetlb_page_tables() can reuse the unmap loop
with its existing mmu_gather.

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


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

	Issue introduced in 5.16 with commit 550a7d60bd5e35a56942dba6d8a26752beb26c9f and fixed in 6.18.64 with commit dd2381dabe0761b6a200a9b4f2eca280e5986faa
	Issue introduced in 5.16 with commit 550a7d60bd5e35a56942dba6d8a26752beb26c9f and fixed in 7.3.5 with commit 71568db3f9d90c373881c6d438db9afc47a1755b
	Issue introduced in 5.16 with commit 550a7d60bd5e35a56942dba6d8a26752beb26c9f and fixed in 7.4-rc2 with commit 92daa8652f88c8cfc05f4899a8408a04b02f211e

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-99703
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/hugetlb.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/dd2381dabe0761b6a200a9b4f2eca280e5986faa
	https://git.kernel.org/stable/c/71568db3f9d90c373881c6d438db9afc47a1755b
	https://git.kernel.org/stable/c/92daa8652f88c8cfc05f4899a8408a04b02f211e

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2026-11-20  5:58 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-20  5:51 CVE-2026-99703: mm/hugetlb: fix mremap deadlock when PMD sharing is possible Greg Kroah-Hartman

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.