CVE-2026-98214

selinux: recheck intermediate backing files on mprotect()

Description

In the Linux kernel, the following vulnerability has been resolved: selinux: recheck intermediate backing files on mprotect() mprotect() can be used to bypass the SELinux checks that mmap() performs against the intermediate layers of a stacked filesystem. mmap() checks every backing layer as the request descends through the stack. mprotect() only has the lowest backing file in vma->vm_file, so it rechecks the top-level user and the lowest mounter, but skips the mounters of every layer in between. With two nested overlayfs mounts and a policy denying mounter_t -> middle_file_t:file { execute }, a direct mmap(PROT_EXEC) is denied: avc: denied { execute } for pid=71 comm="nested_exec" path="/payload" dev="overlay" ino=9 scontext=user_u:base_r:mounter_t tcontext=user_u:object_r:middle_file_t tclass=file permissive=0 while mmap(PROT_NONE) followed by mprotect(PROT_EXEC) succeeds. Preserve each intermediate path, mounter SID and file-description SID in the backing-file security blob, copying the saved entries when another backing layer is opened. Allocate the array only for nested backing files, and release it and the path references in the backing_file_free hook. During mprotect(), recheck fd { use } and the requested inode permissions for every saved mounter, and include the intermediate layers in the execmod checks. Policy for nested stacking may then need to grant intermediate mounters what a direct mmap() already requires, and execmod on intermediate labels for binaries using text relocations. Tested on arm64 QEMU with a small BusyBox initramfs and a purpose-built SELinux policy, on a mainline tree containing commit f2381b546e7e ("fs: fix user path of nested backing files"). [PM: subject tweak]

Key facts

Published
6 Oct 2026
Last changed
19 Oct 2026
Assigned by
Linux
EPSS
0.216% likely to be exploited in the next 30 days, higher than 12.088% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • bc6c380c1159de52a252ed11f19a42c47f60a735 up to but excluding 4d50ebe5a27724e020747ffd61a051dec67cb8ec (affected)
  • 8bacd09f12c27710228562e4d13163e58c5f4a45 up to but excluding 89376fbfdcc1a728e1775f98752cdd90b0930a00 (affected)
  • d844702198395d3f80222777030f69db6be6b709 up to but excluding d127c7e1f3e1231d8ac8b2738e3f00bea12afe74 (affected)
  • 82544d36b1729153c8aeb179e84750f0c085d3b1 up to but excluding c2bbb905af2293549651b614a52ad91e0b462b60 (affected)
  • 82544d36b1729153c8aeb179e84750f0c085d3b1 up to but excluding 78fc54b934bfb2c18aad8154c7302067146946f9 (affected)
  • cd0e707a927a70cdfd8bc5a512a9719a87f5ed51 (affected)
  • 6.6.144 up to but excluding 6.6.158 (affected)
  • 6.12.95 up to but excluding 6.12.112 (affected)
  • 6.18.38 up to but excluding 6.18.54 (affected)
  • 7.0.4 up to but excluding 7.1 (affected)
LinuxLinux
  • Default status: affected
  • 7.1 (affected)
  • 0 up to but excluding 7.1 (unaffected)
  • 6.6.158 up to and including 6.6.* (unaffected)
  • 6.12.112 up to and including 6.12.* (unaffected)
  • 6.18.54 up to and including 6.18.* (unaffected)
  • 7.2.8 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 6 Oct 2026 Published

References