- Veröffentlicht
- 19.11.2026 15:42
- Zuletzt geändert
- 19.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/rmap: don't discard lazyfree THPs at PMD level
__discard_anon_folio_pmd_locked() clears a lazyfree THP's PMD before it
determines whether the folio can be discarded, and restores it if the
folio is dirty or has extra references. It is done under only the PMD
lock and the anon_vma read lock inside try_to_unmap_one() and no mmap lock
is held. The temporarily none PMD causes UAF.
A parallel munmap() or mremap() is supposed to serialize with it on the
PMD lock, but zap_pmd_range() (called by munmap()) and move_page_tables()
(called by mremap()) do not take the lock when they see the temporarily
none PMD and skip the PMD. There is no more page table walk after the
none PMD is restored:
- munmap(): free_pgtables() waits in unlink_anon_vmas() for the anon_vma
lock, then free_pmd_range() drops the restored PMD as bad without
removing the rmap, so the folio keeps a stale mapcount.
- whole-VMA MREMAP_DONTUNMAP: dontunmap_complete() unlinks the source VMA
from its anon_vma while the restored PMD still maps the folio.
- plain mremap(): the THP is not moved but unmapped, so the THP's data is
lost.
In the first two cases, the folio stays mapped, but no VMA that maps it is
linked to its anon_vma. When the anon_vma is freed, it is still reachable
when one rmap walks the folio. Racing lazyfree reclaim against
MREMAP_DONTUNMAP as an unprivileged user reproduces a KASAN use-after-free
in folio_lock_anon_vma_read() as reported in the Closes link.
One solution is to use an invalidated PMD instead of a cleared one until
the discard is committed, but it needs arch fixes first.
1. GUP-fast still follows an invalidated PMD on riscv, LoongArch and s390.
2. sparc64 miscounts thp_pte_count when an invalidated PMD is set again or
cleared.
To keep the fix simple for backport, stop discarding lazyfree THPs at PMD
level instead. try_to_unmap_one() splits the PMD and discards the folio at
PTE level.
unmap_huge_pmd_locked() and __discard_anon_folio_pmd_locked() are left in
place, unused, to minimize this fix for backport and the invalidated PMD
approach is planned as a follow-up series to use them again.
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:13linux6.12.117-1DEBIAN-CVE-2026-99463
Debian:14linux7.3.3-1DEBIAN-CVE-2026-99463
Red Hat:enterprise_linux:10kernelkein Fix bekanntCVE-2026-99463
Red Hat:rhel_els:6kernelkein Fix bekanntCVE-2026-99463
Red Hat:rhel_els:6kernel-abi-whitelistskein Fix bekanntCVE-2026-99463
Red Hat:rhel_els:6kernel-bootwrapperkein Fix bekanntCVE-2026-99463
Red Hat:rhel_els:6kernel-debugkein Fix bekanntCVE-2026-99463
Red Hat:rhel_els:6kernel-debug-develkein Fix bekanntCVE-2026-99463
Red Hat:rhel_els:6kernel-develkein Fix bekanntCVE-2026-99463
Red Hat:rhel_els:6kernel-dockein Fix bekanntCVE-2026-99463
Red Hat:rhel_els:6kernel-firmwarekein Fix bekanntCVE-2026-99463
Red Hat:rhel_els:6kernel-headerskein Fix bekanntCVE-2026-99463
Red Hat:rhel_els:6kernel-kdumpkein Fix bekanntCVE-2026-99463
Red Hat:rhel_els:6kernel-kdump-develkein Fix bekanntCVE-2026-99463
Red Hat:rhel_els:6perfkein Fix bekanntCVE-2026-99463
Red Hat:rhel_els:6python-perfkein Fix bekanntCVE-2026-99463
Weitere betroffene Pakete (3)
CVELinux/Linuxkein Fix bekanntCVE-2026-99463
CVELinux/Linuxkein Fix bekanntCVE-2026-99463
LinuxKernel6.11.0 → 6.12.117, 6.13.0 → 6.18.61, 6.19.0 → 7.3.2CVE-2026-99463
Empfohlene Prüfung
- Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
- Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
- 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.
Referenzen
- git.kernel.org/stable/c/8cf9517996067cfbfc5abdb4cfb3d7e15a7b34a3
- git.kernel.org/stable/c/3594027c292b09d9301b4be80fa8e0c815ffaf2a
- git.kernel.org/stable/c/b8c683bd548268453d50e933aab2e7d50a7ac2be
- git.kernel.org/stable/c/984c0700854e35779a2bcce6b02783e709b6efa2
- git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99463.json
- nvd.nist.gov/vuln/detail/CVE-2026-99463
- security-tracker.debian.org/tracker/CVE-2026-99463
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99463.json
- access.redhat.com/security/cve/CVE-2026-99463
- bugzilla.redhat.com/show_bug.cgi
- www.cve.org/CVERecord