- Veröffentlicht
- 19.11.2026 15:41
- Zuletzt geändert
- 19.11.2026
- EPSS (30 Tage)
- unbekannt
- CVSS-Vektor
- CVSS:3.1/AV:L/AC:L/PR:H/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:
ufs: use u64 for directory size in ufs_last_byte
ufs1_read_inode() and ufs2_read_inode() copy the untrusted 64-bit
on-disk size into inode->i_size. ufs_last_byte() then truncates that
value to an unsigned int before calculating the valid extent of a
directory folio.
A directory size of exactly 4 GiB is truncated to zero. In
ufs_find_entry(), subtracting the requested record length from that zero
forms an endpoint almost 4 GiB beyond the mapped folio. A crafted UFS2
image produces:
BUG: KASAN: use-after-free in ufs_find_entry+0x583/0x6e0 [ufs]
Read of size 1
...
ufs_find_entry
ufs_inode_by_name
ufs_lookup
__lookup_slow
path_lookupat
The KASAN classification reflects that the adjacent physical page was
free; the source-level operation is an out-of-folio read. A controlled
UFS1 test with CONFIG_UFS_FS_WRITE enabled also made ufs_find_entry()
return a directory entry from an adjacent anonymous page. unlink() then
passed that pointer to ufs_delete_entry(), which cleared the adjacent
page's 3
2-bit d_ino. This write result reproduced three out of three
times.
UFS normally requires a privileged mount path. A relevant boundary is
a privileged automounter or image-processing service handling an
attacker-supplied filesystem. The write primitive additionally requires
UFS1 to be mounted read-write with CONFIG_UFS_FS_WRITE enabled; the read
is reachable with read-only UFS2.
Keep the intermediate size arithmetic at 64 bits so non-final pages are
bounded at PAGE_SIZE. With this change, the same controlled tests reach
the real on-disk directory entry and produce no adjacent-page write or
KASAN report. A reproducer and full validation logs are available on
request.
The vulnerable helper is present in v7.2-rc3, v7.1, v6.18.38, v6.12.95,
v6.6.111, and upstream master at 1229e2e57a5c. Runtime reproduction and
fix validation were performed in an x86-64 QEMU guest running v7.2-rc3
with generic KASAN.
Status beim Hersteller
Red Hat stuft seine Produktlinien ein: 1 betroffen, 6 nicht betroffen.
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
Nicht betroffen (6)
Red Hat Enterprise Linux 10Nicht betroffenverwundbarer Code nicht enthaltenkernel
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:12linuxkein Fix bekanntDEBIAN-CVE-2026-99448
Debian:13linux6.12.117-1DEBIAN-CVE-2026-99448
Debian:14linux7.3.3-1DEBIAN-CVE-2026-99448
Red Hat:rhel_els:6kernelkein Fix bekanntCVE-2026-99448
Red Hat:rhel_els:6kernel-abi-whitelistskein Fix bekanntCVE-2026-99448
Red Hat:rhel_els:6kernel-bootwrapperkein Fix bekanntCVE-2026-99448
Red Hat:rhel_els:6kernel-debugkein Fix bekanntCVE-2026-99448
Red Hat:rhel_els:6kernel-debug-develkein Fix bekanntCVE-2026-99448
Red Hat:rhel_els:6kernel-develkein Fix bekanntCVE-2026-99448
Red Hat:rhel_els:6kernel-dockein Fix bekanntCVE-2026-99448
Red Hat:rhel_els:6kernel-firmwarekein Fix bekanntCVE-2026-99448
Red Hat:rhel_els:6kernel-headerskein Fix bekanntCVE-2026-99448
Red Hat:rhel_els:6kernel-kdumpkein Fix bekanntCVE-2026-99448
Red Hat:rhel_els:6kernel-kdump-develkein Fix bekanntCVE-2026-99448
Red Hat:rhel_els:6perfkein Fix bekanntCVE-2026-99448
Red Hat:rhel_els:6python-perfkein Fix bekanntCVE-2026-99448
Weitere betroffene Pakete (3)
CVELinux/Linuxkein Fix bekanntCVE-2026-99448
CVELinux/Linuxkein Fix bekanntCVE-2026-99448
LinuxKernel2.6.18 → 6.12.117, 6.13.0 → 6.18.61, 6.19.0 → 7.3.2CVE-2026-99448
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/ae50223c56b9a1c27d4f824c9e2fbbefc8686891
- git.kernel.org/stable/c/c792858491ee39e8f6e1547c45422595cf25b415
- git.kernel.org/stable/c/ac2859c61ecf52a9e39b44b35c981dbfeb8ad54b
- git.kernel.org/stable/c/1eff23433e73d7da4f9e3529d2701e34962b161f
- git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99448.json
- nvd.nist.gov/vuln/detail/CVE-2026-99448
- security-tracker.debian.org/tracker/CVE-2026-99448
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99448.json
- access.redhat.com/security/cve/CVE-2026-99448
- bugzilla.redhat.com/show_bug.cgi
- www.cve.org/CVERecord