← Übersicht Linux Kernel, Red Hat Enterprise Linux

mm/userfaultfd: only allocate anon_vma in CoW mappings

CVE-2026-99580 · DEBIAN-CVE-2026-99580

Hoch · CVSS 7.8 Red Hat: Important Lokal Kein Fix bekannt

Veröffentlicht
20.11.2026 06:49
Zuletzt geändert
20.11.2026
EPSS (30 Tage)
unbekannt
CVSS-Vektor
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Beschreibung

Originaltext der Quelle, nicht übersetzt.

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.

Status beim Hersteller

Red Hat stuft seine Produktlinien ein: 3 betroffen, 5 nicht betroffen.

Red Hat Enterprise Linux 10 BetroffenFix ausstehend kernel
Red Hat Enterprise Linux 6 BetroffenFix ausstehend kernel, kernel-abi-whitelists, kernel-bootwrapper, kernel-debug, kernel-debug-devel, kernel-devel, kernel-doc, kernel-firmware, kernel-headers, kernel-kdump, kernel-kdump-devel, perf, python-perf
Red Hat OpenShift Container Platform 5 BetroffenFix ausstehend openshift/ose-rhel-coreos-10
Nicht betroffen (5)
Red Hat Enterprise Linux 7Nicht betroffenverwundbarer Code nicht enthaltenbpftool, kernel, kernel-abi-whitelists, kernel-bootwrapper, kernel-debug, kernel-debug-devel, kernel-devel, kernel-doc, kernel-headers, kernel-kdump, kernel-kdump-devel, kernel-rt, kernel-rt-debug, kernel-rt-debug-devel, kernel-rt-debug-kvm, kernel-rt-devel, kernel-rt-doc, kernel-rt-kvm, kernel-rt-trace, kernel-rt-trace-devel, kernel-rt-trace-kvm, kernel-tools, kernel-tools-libs, kernel-tools-libs-devel, perf und 1 weitere
Red Hat Enterprise Linux 8Nicht betroffenverwundbarer Code nicht enthaltenbpftool, kernel, kernel-abi-stablelists, kernel-abi-whitelists, kernel-core, kernel-cross-headers, kernel-debug, kernel-debug-core, kernel-debug-devel, kernel-debug-modules, kernel-debug-modules-extra, kernel-debug-modules-internal, kernel-devel, kernel-doc, kernel-headers, kernel-ipaclones-internal, kernel-modules, kernel-modules-extra, kernel-modules-internal, kernel-rt, kernel-rt-core, kernel-rt-debug, kernel-rt-debug-core, kernel-rt-debug-devel, kernel-rt-debug-kvm und 21 weitere
Red Hat Enterprise Linux 9Nicht betroffenverwundbarer Code nicht enthaltenbpftool, kernel, kernel-64k, kernel-64k-core, kernel-64k-debug, kernel-64k-debug-core, kernel-64k-debug-devel, kernel-64k-debug-devel-matched, kernel-64k-debug-modules, kernel-64k-debug-modules-core, kernel-64k-debug-modules-extra, kernel-64k-debug-modules-internal, kernel-64k-debug-modules-partner, kernel-64k-devel, kernel-64k-devel-matched, kernel-64k-modules, kernel-64k-modules-core, kernel-64k-modules-extra, kernel-64k-modules-internal, kernel-64k-modules-partner, kernel-abi-stablelists, kernel-core, kernel-cross-headers, kernel-debug, kernel-debug-core und 82 weitere
Red Hat OpenShift Container Platform 4Nicht betroffenverwundbarer Code nicht enthaltenopenshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9
Red Hat OpenShift Container Platform 5Nicht betroffenverwundbarer Code nicht enthaltenopenshift/ose-rhel-coreos-9

Betroffene Pakete im beobachteten Stack

Debian:13linuxkein Fix bekanntDEBIAN-CVE-2026-99580
Debian:14linuxkein Fix bekanntDEBIAN-CVE-2026-99580
Red Hat:enterprise_linux:10kernelkein Fix bekanntCVE-2026-99580
Red Hat:rhel_els:6kernelkein Fix bekanntCVE-2026-99580
Red Hat:rhel_els:6kernel-abi-whitelistskein Fix bekanntCVE-2026-99580
Red Hat:rhel_els:6kernel-bootwrapperkein Fix bekanntCVE-2026-99580
Red Hat:rhel_els:6kernel-debugkein Fix bekanntCVE-2026-99580
Red Hat:rhel_els:6kernel-debug-develkein Fix bekanntCVE-2026-99580
Red Hat:rhel_els:6kernel-develkein Fix bekanntCVE-2026-99580
Red Hat:rhel_els:6kernel-dockein Fix bekanntCVE-2026-99580
Red Hat:rhel_els:6kernel-firmwarekein Fix bekanntCVE-2026-99580
Red Hat:rhel_els:6kernel-headerskein Fix bekanntCVE-2026-99580
Red Hat:rhel_els:6kernel-kdumpkein Fix bekanntCVE-2026-99580
Red Hat:rhel_els:6kernel-kdump-develkein Fix bekanntCVE-2026-99580
Red Hat:rhel_els:6perfkein Fix bekanntCVE-2026-99580
Red Hat:rhel_els:6python-perfkein Fix bekanntCVE-2026-99580
Weitere betroffene Pakete (3)
CVELinux/Linuxkein Fix bekanntCVE-2026-99580
CVELinux/Linuxkein Fix bekanntCVE-2026-99580
LinuxKernel6.9.0 → 6.12.118, 6.13.0 → 6.18.64, 6.19.0 → 7.3.5CVE-2026-99580

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Lokal) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.