CVE-2026-98215selinux: preserve user SID across nested backing files
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 89% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 11 days later
· 11 days later
Published
- 13 days later
· 13 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected bc6c380c1159de52a252ed11f19a42c47f60a735 – < caa1b913d90d5dc07073733326d2af0f0288f089
- affected 8bacd09f12c27710228562e4d13163e58c5f4a45 – < 6aaeec59aadcd1eafc18b049f1b759fb6b9d9569
- affected d844702198395d3f80222777030f69db6be6b709 – < 9d99b770e7b67b00bdef9005b928aad13e1d679b
- affected 82544d36b1729153c8aeb179e84750f0c085d3b1 – < ff20d16b2e8230c034e21540043df47222dcc09b
- affected 82544d36b1729153c8aeb179e84750f0c085d3b1 – < 8c0c602202b9a4909b00bc3354e3c0355bc69e65
- affected cd0e707a927a70cdfd8bc5a512a9719a87f5ed51
- affected 6.6.144 – < 6.6.158
- affected 6.12.95 – < 6.12.112
- affected 6.18.38 – < 6.18.54
- affected 7.0.4 – < 7.1
- affected 7.1
- unaffected < 7.1
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.112 – ≤ 6.12.*
- unaffected 6.18.54 – ≤ 6.18.*
- unaffected 7.2.8 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References5
- https://git.kernel.org/stable/c/caa1b913d90d5dc07073733326d2af0f0288f089 (opens in a new tab)
- https://git.kernel.org/stable/c/6aaeec59aadcd1eafc18b049f1b759fb6b9d9569 (opens in a new tab)
- https://git.kernel.org/stable/c/9d99b770e7b67b00bdef9005b928aad13e1d679b (opens in a new tab)
- https://git.kernel.org/stable/c/ff20d16b2e8230c034e21540043df47222dcc09b (opens in a new tab)
- https://git.kernel.org/stable/c/8c0c602202b9a4909b00bc3354e3c0355bc69e65 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-93143 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98215)Record last updated .