Skip to main content
VulnerabilityPublished Updated

CVE-2026-46054: Linux kernel · selinux: fix overlayfs mmap() and mprotect() access checks

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 7.1 High · fixed in d844702198395d3f80222777030f69db6be6b709 : patch Linux kernel soon.

Data as of 26 Oct 2026, 17:30 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in d844702198395d3f80222777030f69db6be6b709, cd0e707a927a70cdfd8bc5a512a9719a87f5ed51, bc6c380c1159de52a252ed11f19a42c47f60a735 +2
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 2f502839e85ab265f03f25f30d6463154aee5473, < d844702198395d3f80222777030f69db6be6b709
Fixed in
  • d844702198395d3f80222777030f69db6be6b709
LinuxLinuxAffected
  • ≥ 2f502839e85ab265f03f25f30d6463154aee5473, < cd0e707a927a70cdfd8bc5a512a9719a87f5ed51
Fixed in
  • cd0e707a927a70cdfd8bc5a512a9719a87f5ed51
LinuxLinuxAffected
  • ≥ 2f502839e85ab265f03f25f30d6463154aee5473, < bc6c380c1159de52a252ed11f19a42c47f60a735
Fixed in
  • bc6c380c1159de52a252ed11f19a42c47f60a735
LinuxLinuxAffected
  • ≥ 2f502839e85ab265f03f25f30d6463154aee5473, < 82544d36b1729153c8aeb179e84750f0c085d3b1
Fixed in
  • 82544d36b1729153c8aeb179e84750f0c085d3b1
LinuxLinuxAffected
  • ≥ 2f502839e85ab265f03f25f30d6463154aee5473, < 8bacd09f12c27710228562e4d13163e58c5f4a45
Fixed in
  • 8bacd09f12c27710228562e4d13163e58c5f4a45
LinuxLinuxAffected
  • =4.19
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: selinux: fix overlayfs mmap() and mprotect() access checks The existing SELinux security model for overlayfs is to allow access if the current task is able to access the top level file (the "user" file) and the mounter's credentials are sufficient to access the lower level file (the "backing" file). Unfortunately, the current code does not properly enforce these access controls for both mmap() and mprotect() operations on overlayfs filesystems. This patch makes use of the newly created security_mmap_backing_file() LSM hook to provide the missing backing file enforcement for mmap() operations, and leverages the backing file API and new LSM blob to provide the necessary information to properly enforce the mprotect() access controls.

References

Community reviews

Loading reviews…