mm/hugetlb: fix mremap deadlock when PMD sharing is possible
Summary
| CVE | CVE-2026-99703 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-11-20 06:18:06 UTC |
| Updated | 2026-11-20 06:18:06 UTC |
| 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 550a7d60bd5e35a56942dba6d8a26752beb26c9f dd2381dabe0761b6a200a9b4f2eca280e5986faa git |
Not specified |
| CNA |
Linux |
Linux |
affected 550a7d60bd5e35a56942dba6d8a26752beb26c9f 71568db3f9d90c373881c6d438db9afc47a1755b git |
Not specified |
| CNA |
Linux |
Linux |
affected 550a7d60bd5e35a56942dba6d8a26752beb26c9f 92daa8652f88c8cfc05f4899a8408a04b02f211e git |
Not specified |
| CNA |
Linux |
Linux |
affected 5.16 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.16 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.64 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3.5 7.3.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.4-rc2 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/92daa8652f88c8cfc05f4899a8408a04b02f211e |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/71568db3f9d90c373881c6d438db9afc47a1755b |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/dd2381dabe0761b6a200a9b4f2eca280e5986faa |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.