Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 82544d36b1729153c8aeb179e84750f0c085d3b1, 8bacd09f12c27710228562e4d13163e58c5f4a45, bc6c380c1159de52a252ed11f19a42c47f60a735.

Low priority for now. Upgrade to Linux Linux 82544d36b1729153c8aeb179e84750f0c085d3b1, 8bacd09f12c27710228562e4d13163e58c5f4a45, bc6c380c1159de52a252ed11f19a42c47f60a735 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
May 27, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.1
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-46054

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.19 and later · before 7.0.4

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.19affected
    • 2f502839e85ab265f03f25f30d6463154aee5473 and later · before bc6c380c1159de52a252ed11f19a42c47f60a735affected · git
    • 2f502839e85ab265f03f25f30d6463154aee5473 and later · before 8bacd09f12c27710228562e4d13163e58c5f4a45affected · git
    • 2f502839e85ab265f03f25f30d6463154aee5473 and later · before d844702198395d3f80222777030f69db6be6b709affected · git
    • 2f502839e85ab265f03f25f30d6463154aee5473 and later · before cd0e707a927a70cdfd8bc5a512a9719a87f5ed51affected · git
    • 2f502839e85ab265f03f25f30d6463154aee5473 and later · before 82544d36b1729153c8aeb179e84750f0c085d3b1affected · git
    • before 4.19not affected · semver
    • 6.6.144 and later · up to and including 6.6.*not affected · semver
    • 6.12.95 and later · up to and including 6.12.*not affected · semver
    • 6.18.38 and later · up to and including 6.18.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernelbefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.28.1.el10_26.12.0-211.28.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-46051May 27, 2026 · md/raid5: fix soft lockup in retry_aligned_read()
    22Monitor
  • ← EarlierCVE-2026-46052May 27, 2026 · ceph: only d_add() negative dentries when they are unhashed
    30Monitor
  • Later →CVE-2026-46056May 27, 2026 · Bluetooth: hci_event: fix potential UAF in SSP passkey handlers
    35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux82544d36b1729153c8aeb179e84750f0c085d3b1Vendor (CNA)
Linux Linux8bacd09f12c27710228562e4d13163e58c5f4a45Vendor (CNA)
Linux Linuxbc6c380c1159de52a252ed11f19a42c47f60a735Vendor (CNA)
Linux Linuxcd0e707a927a70cdfd8bc5a512a9719a87f5ed51Vendor (CNA)
Linux Linuxd844702198395d3f80222777030f69db6be6b709Vendor (CNA)
almalinux:kernel6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux6.12.95-1 · Debian:13Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-211.22.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-211.22.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-211.22.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-211.22.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-211.22.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-211.22.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-211.22.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-211.22.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-211.22.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo0:6.12.0-211.22.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo-common-aarch640:6.12.0-211.22.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:6.12.0-211.22.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)

+2

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-461741 days apartx86/CPU/AMD: Prevent improper isolation of shared resources in Zen2's op cache
    35Monitor
  • CVE-2026-6382953 days apartnet: ip_gre: require CAP_NET_ADMIN in the device netns for changelink
    35Monitor
  • CVE-2026-6392153 days apartip6: vti: Use ip6_tnl.net in vti6_siocdevprivate().
    35Monitor
  • CVE-2026-6394153 days apartKVM: arm64: Correctly cap ZCR_EL2 provided by a guest hypervisor
    35Monitor
  • CVE-2026-6404253 days apartvfio/pci: Check BAR resources before exporting a DMABUF
    35Monitor
  • CVE-2026-3178863 days apartxen/privcmd: restrict usage in unprivileged domU
    32Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
None

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records