Skip to main content
No exploitation reportedFix availableAwaiting NVD analysis

CVE-2026-99580

mm/userfaultfd: only allocate anon_vma in CoW mappings

No exploitation reported by the sources we read.

  • Published2026-11-20
  • Fixed in7.3.5 · 6.18.64 · 6.12.118

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

In the Linux kernel, the following vulnerability has been resolved: mm/userfaultfd: only allocate anon_vma in CoW mappings find_vma_and_prepare_anon() can end up allocating an anon_vma in VMAs that are not CoW mappings, which is wrong. If we have a MAP_SHARED R/O file mapped, we lack VM_SHARED (but do have VM_MAYSHARE) and lack VM_MAYWRITE. While uffd later rejects such mappings (uffd registration requires VM_MAYWRITE, see comment in validate_dst_vma) find_vma_and_prepare_anon() still wrongly allocates an anon vma before it validates the vma. This in turn later confuses copy_page_range()->vma_needs_copy() such that we end up calling copy_hugetlb_page_range() with ranges that actually do not contain *any* per-pagetable information that would require copying, which is the basis for PMD-table sharing in the first place. copy_hugetlb_page_range() should not have to worry about shared PMD tables at all: it doesn't make any sense to copy page tables that are shared, as they can be fully recreated later. Ending up in the function with shareable page tables is the real issue. If a destination PMD table is shared in copy_hugetlb_page_range(), it might get concurrently unshared as we are not holding relevant locks, resulting in us using a page table that is no longer mapped and possibly freed after calling: dst_pte = huge_pte_alloc(dst, dst_vma, addr, sz); To fix it, do not allocate an anon_vma in non-CoW mappings and add a safety guard to copy_hugetlb_page_range(), making sure that we never end up messing with shared PMD tables in there. Before commit 867a43a34ff8a ("userfaultfd: use per-vma locks in userfaultfd operations") we would always validate the VMA before allocating an anon_vma, and consequently never wrongly allocate an anon_vma. As uffd_lock_vma() is part of the same lookup machinery and also contains a misleading VM_SHARED check, change that one as well directly for consistency. A follow-up cleanup will stop taking the hugetlb_vma_lock_read(src_vma) lock in copy_hugetlb_page_range() entirely. Further, the usage of VM_SHARED in userfaultfd code should be cleaned up later to focus on CoW vs. non-CoW mappings.

Timeline

dates in UTC
  1. 2026-11-2005:49CVE publishedCNA

Versions per branch

OSV
Linux kernel
BranchAffectedFixed in
7.3≥ 6.19.0, < 7.3.57.3.5
6.x≥ 6.13.0, < 6.18.646.18.64
6.x≥ 6.9.0, < 6.12.1186.12.118

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA2 products

As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Linuxother versions: not affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • ≥ 867a43a34ff8a38772212045262b2c9b77807ea3, < a90e7044b34f801fbafcb682e8ee827a6db26002fixed in a90e7044b34f801fbafcb682e8ee827a6db26002git
    • ≥ 867a43a34ff8a38772212045262b2c9b77807ea3, < 3bf446c8ce64938f86439906d730a2cd5c0b31e2fixed in 3bf446c8ce64938f86439906d730a2cd5c0b31e2git
    • ≥ 867a43a34ff8a38772212045262b2c9b77807ea3, < 20704188d669ed74a624fd67dfa4711bcb1087b6fixed in 20704188d669ed74a624fd67dfa4711bcb1087b6git
    • ≥ 867a43a34ff8a38772212045262b2c9b77807ea3, < 514c9247db305922591d806ec65d3c3fe420538dfixed in 514c9247db305922591d806ec65d3c3fe420538dgit
  • Linuxother versions: affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • = 6.9no fix stated

    Not affected < 6.9 · ≥ 6.12.118, ≤ 6.12.* · ≥ 6.18.64, ≤ 6.18.* · ≥ 7.3.5, ≤ 7.3.* · ≥ 7.4-rc1

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE terms of useCVE recordupdated 2026-11-20

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • linuxDebian:14all versions · no fixed version listed
  • linuxDebian:13all versions · fixed in 6.12.118-1
  • linux-ltsAlpaquita:streamfrom 6.18.62-r0 · fixed in 6.18.64-r0
  • linux-ltsAlpaquita:25from 6.12.115-r0 · no fixed version listed

Vendor advisories

  • CVE-2026-99580 Red Hat Product Security16 known affected

    kernel: kernel: privilege escalation via improper memory allocation in userfaultfd

    kernel.src as a component of Red Hat Enterprise Linux 10 · kernel as a component of Red Hat Enterprise Linux 6 · kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6 · +13 more

Full record on NVD

Fix

  1. Update Linux kernel to 7.3.5 · 6.18.64 · 6.12.118
  2. No fix available, says the vendor Red Hat Product Security CVE-2026-99580 · 16 productsAffected

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published
2026-11-20
Last modified
2026-11-22
NVD status
Received
GitHub advisory
GHSA-g42q-c6pj-qg24

Frequently asked questions

What is CVE-2026-99580?

In the Linux kernel, the following vulnerability has been resolved: mm/userfaultfd: only allocate anon_vma in CoW mappings find_vma_and_prepare_anon() can end up allocating an anon_vma in VMAs that are not CoW mappings, which is wrong. If we have a MAP_SHARED R/O file mapped, we lack VM_SHARED (but do have VM_MAYSHARE) and lack VM_MAYWRITE. While uffd later rejects such mappings (uffd registration requires VM_MAYWRITE, see comment in validate_dst_vma) find_vma_and_prepare_anon() still wrongly allocates an anon vma before it validates the vma. This in turn later confuses copy_page_range()->vma_needs_copy() such that we end up calling copy_hugetlb_page_range() with ranges that actually do not contain *any* per-pagetable information that would require copying, which is the basis for PMD-table sharing in the first place. copy_hugetlb_page_range() should not have to worry about shared PMD tables at all: it doesn't make any sense to copy page tables that are shared, as they can be fully recreated later. Ending up in the function with shareable page tables is the real issue. If a destination PMD table is shared in copy_hugetlb_page_range(), it might get concurrently unshared as we are not holding relevant locks, resulting in us using a page table that is no longer mapped and possibly freed after calling: dst_pte = huge_pte_alloc(dst, dst_vma, addr, sz); To fix it, do not allocate an anon_vma in non-CoW mappings and add a safety guard to copy_hugetlb_page_range(), making sure that we never end up messing with shared PMD tables in there. Before commit 867a43a34ff8a ("userfaultfd: use per-vma locks in userfaultfd operations") we would always validate the VMA before allocating an anon_vma, and consequently never wrongly allocate an anon_vma. As uffd_lock_vma() is part of the same lookup machinery and also contains a misleading VM_SHARED check, change that one as well directly for consistency. A follow-up cleanup will stop taking the hugetlb_vma_lock_read(src_vma) lock in copy_hugetlb_page_range() entirely. Further, the usage of VM_SHARED in userfaultfd code should be cleaned up later to focus on CoW vs. non-CoW mappings.

Is CVE-2026-99580 actively exploited?

Active exploitation of CVE-2026-99580 has not been confirmed. Its EPSS score was 0.2% on 2026-11-21, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-99580?

CVE-2026-99580 has a CVSS v3 base score of 7.8 (High severity), with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Running Linux kernel? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website checks · 250 API requests/month

Sources for this record