- Veröffentlicht
- 20.11.2026 06:50
- 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:N/I:N/A:H
Beschreibung
Originaltext der Quelle, nicht übersetzt.
In the Linux kernel, the following vulnerability has been resolved:
mm: memory: fix truncation removing mapped folios
Ayush reported an issue that shmem/tmpfs folios are still mapped when
truncating them on production:
"
BUG: Bad page cache in process ... pfn:...
page dumped because: still mapped when deleted
"
I reproduced the issue with Ayush's reproducer [1] with the latest
mm-unstable branch, and I got the following crash info. From the dump
message, we can see that truncate_inode_folio() is really trying to remove
mapped folios, which is incorrect.
"
[ 189.171977] page: refcount:3 mapcount:1 mapping:00000000fe168ee1
index:0x3880 pfn:0x191647
[ 189.171995] memcg:ffff0000cc073d40
[ 189.171997] aops:shmem_aops ino:3c01 dentry name(?):"memfd:runsc-memory"
[ 189.172006] flags: 0x17fffef0002022d(locked|referenced|uptodate|lru|
workingset|swapbacked|node=0|zone=2|lastcpupid=0x3ffff)
.......
[ 189.172017] page dumped because: VM_BUG_ON_FOLIO(folio_mapped(folio))
[ 189.172026] ------------[ cut here ]------------
[ 189.172027] kernel BUG at mm/filemap.c:155!
[ 189.172057] Internal error: Oops - BUG: 00000000f2000800 [#1] SMP
.......
[ 189.177721] CPU: 3 UID: 0 PID: 5521 Comm: repro Kdump: loaded Tainted:
7.3.0-rc4+ #277 PREEMPT(lazy)
.......
[ 189.183986] Call trace:
[ 189.184124] filemap_unaccount_folio+0xf0/0x1e8 (P)
[ 189.184391] __filemap_remove_folio+0x34/0x160
[ 189.184633] filemap_remove_folio+0x4c/0xb0
[ 189.184859] truncate_inode_folio+0x34/0x58
[ 189.185087] shmem_undo_range+0x220/0x658
[ 189.185308] shmem_fallocate+0x2f0/0x470
[ 189.185527] vfs_fallocate+0x128/0x328
......
[ 189.187078] el0t_64_sync+0x184/0x188
"
After analysis, I believe the race exists between truncation and
MADV_DONTNEED, and shmem's ->map_pages() merely makes the issue easier to
reproduce. Since MADV_DONTNEED synchronously releases the pagetable page
before calling tlb_flush_rmaps(), this could cause another thread's
truncation to skip zap_pte_range() (due to pmd is none) but still observe
the folio's mapcount as non-zero. A possible race scenario is as follows:
CPU 0 CPU 1
shmem_fallocate madvise_dontneed_single_vma
unmap_mapping_range .......
......
(filemap_map_pages() remap folios)
zap_pte_range
truncate_inode_folio zap_empty_pte_table(pmd clear)
unmap_mapping_folio
......
zap_pmd_range (saw pmd none, skip)
filemap_remove_folio
BUG_ON(folio_mapped)
tlb_flush_rmaps(remove rmaps)
To fix this issue, we should move the pmd clear operation (via
zap_empty_pte_table()) to after tlb_flush_rmaps() and use
sync_with_folio_pmd_zap() to sync with concurrent zapping, so that when we
find a pmd_none() while unmapping a folio without holding the PTL, the
folio's mappings are guaranteed to have been removed via
tlb_flush_rmaps().
Meanwhile move the second pmd_none() check to where it belongs: if
splitting zapped the PMD.
Status beim Hersteller
Red Hat stuft seine Produktlinien ein: 3 betroffen, 5 nicht betroffen.
Red Hat Enterprise Linux 10
BetroffenFix zurückgestellt
kernel
Red Hat Enterprise Linux 6
Betroffenaußerhalb des Supports
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 zurückgestellt
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:14linuxkein Fix bekanntDEBIAN-CVE-2026-99705
Red Hat:enterprise_linux:10kernelkein Fix bekanntCVE-2026-99705
Red Hat:rhel_els:6kernelkein Fix bekanntCVE-2026-99705
Red Hat:rhel_els:6kernel-abi-whitelistskein Fix bekanntCVE-2026-99705
Red Hat:rhel_els:6kernel-bootwrapperkein Fix bekanntCVE-2026-99705
Red Hat:rhel_els:6kernel-debugkein Fix bekanntCVE-2026-99705
Red Hat:rhel_els:6kernel-debug-develkein Fix bekanntCVE-2026-99705
Red Hat:rhel_els:6kernel-develkein Fix bekanntCVE-2026-99705
Red Hat:rhel_els:6kernel-dockein Fix bekanntCVE-2026-99705
Red Hat:rhel_els:6kernel-firmwarekein Fix bekanntCVE-2026-99705
Red Hat:rhel_els:6kernel-headerskein Fix bekanntCVE-2026-99705
Red Hat:rhel_els:6kernel-kdumpkein Fix bekanntCVE-2026-99705
Red Hat:rhel_els:6kernel-kdump-develkein Fix bekanntCVE-2026-99705
Red Hat:rhel_els:6perfkein Fix bekanntCVE-2026-99705
Red Hat:rhel_els:6python-perfkein Fix bekanntCVE-2026-99705
Weitere betroffene Pakete (3)
CVELinux/Linuxkein Fix bekanntCVE-2026-99705
CVELinux/Linuxkein Fix bekanntCVE-2026-99705
LinuxKernel6.14.0 → 6.18.64, 6.19.0 → 7.3.5CVE-2026-99705
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/8011e987026b65f59ea6b6082c777807a008b227
- git.kernel.org/stable/c/b57cfd4da476a4636bf1ed69dee176cc266e5a06
- git.kernel.org/stable/c/243cf1f67b365668389832463fc31cbb9fec47af
- git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99705.json
- nvd.nist.gov/vuln/detail/CVE-2026-99705
- security-tracker.debian.org/tracker/CVE-2026-99705
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99705.json
- access.redhat.com/security/cve/CVE-2026-99705
- bugzilla.redhat.com/show_bug.cgi
- www.cve.org/CVERecord