CVE-2026-98215
In the Linux kernel, the following vulnerability has been resolved: selinux: preserve user SID across nested backing files SELinux saves the user file SID in a backing-file security blob so it remains available after mmap() replaces vma->vm_file with a backing file. For nested backing files (overlayfs over overlayfs, or FUSE passthrough backed by overlayfs), user_file may itself be a backing file. Its fsec->sid is the SID of the mounter that opened it, rather than the user that opened the top-level file. mprotect() then checks fd { use } against the mounter SID. This can incorrectly deny access without a domain transition, or check the wrong target SID after one. Copy the saved user SID when user_file is a backing file. Keep using the regular file SID for the first backing layer. With two nested overlayfs mounts and SELinux enforcing, mprotect(PROT_READ) returns EACCES with an fd { use } denial against the mounter SID. With this change, mprotect() succeeds. Tested on arm64 QEMU with a small BusyBox initramfs and a purpose-built SELinux policy. The original test was also repeated with Fedora Cloud Base 44 userspace and gave the same result.
Affected versions
Linux kernel versions
6.6.144,
6.12.95,
6.18.38,
7.0.4,
7.1
and later are affected. Fixed in
6.6.158,
6.12.112,
6.18.54,
7.2.8,
7.3-rc4
and their respective stable series.
References
5 totalFrequently asked questions
-
What is CVE-2026-98215?
CVE-2026-98215 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 6.6.144 onward and has been patched in 6.6.158, 6.12.112, 6.18.54 and others. CVE-2026-98215 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-98215?
Yes. CVE-2026-98215 has been patched. Fixed versions include 6.6.158, 6.12.112, 6.18.54 and others. If you are running Linux kernel 6.6.144 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-98215 actively exploited?
No. CVE-2026-98215 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.