- 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:N/I:N/A:L
Beschreibung
Originaltext der Quelle, nicht übersetzt.
In the Linux kernel, the following vulnerability has been resolved:
ovl: fix whiteout creation in casefolded directories
unlink and rmdir fail with EINVAL on an overlay with casefolded
(case-insensitive) layers, if the name exists in a lower layer.
Casefolded layers need CONFIG_UNICODE. Root can mount such an overlay,
and so can an unprivileged user in a user namespace, with tmpfs layers.
Overlayfs does not change a lower layer. To remove a name that exists
there, it hides the name with a marker file, a whiteout. It creates the
whiteout in the work directory, a scratch directory on the upper
filesystem, and renames it over the name in the upper directory:
- ovl_whiteout() creates the whiteout with mknod, or as a hard link to
an earlier whiteout.
- ovl_cleanup_and_whiteout() then prepares the rename with
start_renaming_two_dentries(), which returns -EINVAL if the source or
the target dentry is unhashed, that is, not in the dentry hash table.
With casefolded directories, both dentries can be unhashed:
- The target. Lookup in a casefolded directory leaves a negative dentry
unhashed, so the rename target is unhashed if the name does not exist
in the upper directory.
- The source, which is the new whiteout. tmpfs hashes a dentry when
mknod or link makes it positive, but ext4 does not, so on ext4 the
source is unhashed as well.
The cleanup after the failure also refuses an unhashed dentry, so on
ext4 the whiteout is left behind in the work directory.
Reproduced with rm and rmdir on casefolded tmpfs and ext4 layers, also
as uid 1000 in a user namespace.
Fix this by creating the whiteout with ovl_create_temp(), which repeats
the lookup if the new dentry is unhashed. Prepare the rename with
start_renaming_dentry(), which looks up the target name with the
directories locked. The caller looked the name up without a lock, so
return -ESTALE if the name now refers to a different inode.
[amir: pass the name used for lookup instead of taking a name snapshot]
Status beim Hersteller
Red Hat stuft seine Produktlinien ein: 7 nicht betroffen.
Nicht betroffen (7)
Red Hat Enterprise Linux 10Nicht betroffenverwundbarer Code nicht enthaltenkernel
Red Hat Enterprise Linux 6Nicht betroffenverwundbarer Code nicht enthaltenkernel, 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 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-10, openshift/ose-rhel-coreos-9
Betroffene Pakete im beobachteten Stack
Debian:14linuxkein Fix bekanntDEBIAN-CVE-2026-99639
Weitere betroffene Pakete (3)
CVELinux/Linuxkein Fix bekanntCVE-2026-99639
CVELinux/Linuxkein Fix bekanntCVE-2026-99639
LinuxKernel6.19.0 → 7.3.5CVE-2026-99639
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/48bd1823237fb076db6e109e35c59b1bc08f550a
- git.kernel.org/stable/c/e803c82dcdd15e87b48fca1ea8d2cfe6a7ed83d4
- git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99639.json
- nvd.nist.gov/vuln/detail/CVE-2026-99639
- security-tracker.debian.org/tracker/CVE-2026-99639
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99639.json
- access.redhat.com/security/cve/CVE-2026-99639
- bugzilla.redhat.com/show_bug.cgi
- www.cve.org/CVERecord