Skip to main content
VulnerabilityPublished

CVE-2026-99580: Linux kernel · mm/userfaultfd: only allocate anon_vma in CoW mappings

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99580· High

Not known to be exploited · fixed in a90e7044b34f801fbafcb682e8ee827a6db26002 : patch Linux kernel soon.

Data as of 20 Nov 2026, 07:34 UTC

Severity
High

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in a90e7044b34f801fbafcb682e8ee827a6db26002, 20704188d669ed74a624fd67dfa4711bcb1087b6, 514c9247db305922591d806ec65d3c3fe420538d +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Linux kernel to a90e7044b34f801fbafcb682e8ee827a6db26002, 20704188d669ed74a624fd67dfa4711bcb1087b6, 514c9247db305922591d806ec65d3c3fe420538d or 3bf446c8ce64938f86439906d730a2cd5c0b31e2.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 867a43a34ff8a38772212045262b2c9b77807ea3, < a90e7044b34f801fbafcb682e8ee827a6db26002
Fixed in
  • a90e7044b34f801fbafcb682e8ee827a6db26002
LinuxLinuxAffected
  • ≥ 867a43a34ff8a38772212045262b2c9b77807ea3, < 20704188d669ed74a624fd67dfa4711bcb1087b6
Fixed in
  • 20704188d669ed74a624fd67dfa4711bcb1087b6
LinuxLinuxAffected
  • ≥ 867a43a34ff8a38772212045262b2c9b77807ea3, < 514c9247db305922591d806ec65d3c3fe420538d
Fixed in
  • 514c9247db305922591d806ec65d3c3fe420538d
LinuxLinuxAffected
  • ≥ 867a43a34ff8a38772212045262b2c9b77807ea3, < 3bf446c8ce64938f86439906d730a2cd5c0b31e2
Fixed in
  • 3bf446c8ce64938f86439906d730a2cd5c0b31e2
LinuxLinuxAffected
  • =6.9
Fixed in–

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.

References

Community reviews

Loading reviews…