Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-46054 is a high-severity Missing Authorization (CWE-862) vulnerability in Linux Kernel. Its CVSS base score is 7.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Regsvcs/Regasm (T1218.009); ranked at the 2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) and AC-25 (Reference Monitor) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-32436
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 6 hardening rules · 3 OS baselines
V6.2.2V8.3.3
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
Ensuring access decisions are applied to every request structurally prevents the product from taking unexpected paths when privileges are lacking.
A reference monitor that is always invoked guarantees privilege checks occur, eliminating the root condition for improper insufficient-privilege handling.
Access enforcement directly stops code from proceeding on insufficient privileges by applying authorization checks before resource access.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Defining, enforcing and reviewing access permissions with least privilege directly prevents code paths that mishandle insufficient privileges.
Runtime monitoring of software and data surfaces adverse events triggered by unhandled permission failures.
Generating logs of permission-related events enables detection and analysis of improper handling.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Security testing can detect missing or incorrect privilege handling.
A.8.3's purpose is to ensure only authorized access, and its guidance directly mandates the authorization checks that CWE-862 describes as missing, so a well-implemented access restriction control fully blocks exploitation of the missing authorization weakness.
Requiring formal authorization of every access request before rights are granted ensures that checks for required permissions are performed, preventing missing authorization checks from being introduced.
By requiring competent outsiders to verify that every function enforces the need-to-know principle, the control lowers the likelihood that missing authorization checks persist undetected.
Secure-coding standards require proper permission checks before resource access.
Requiring evidence of minimum security capabilities and acceptance testing ensures that missing or bypassed authorization checks are detected before the delivered software is accepted.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over our cross-walk; rows rated `none` are excluded, and each rule says how its mapping was checked.
Definition changed on 29 October 2026. Until then this section listed every rule rated above none, partial included. From that date it lists rules whose mapping is rated full or mostly and checked at llm_unverified or higher; partial mappings show when you ask.
No rule maps to these weaknesses at full or mostly. Tick the option above to see the partial mappings.
Oracle Linux 8 (2 partial rules)
- V-248548 OL 8 must use a Linux Security Module configured to enforce limits on system services. blocks CWE-280
- V-248596 OL 8 must enable the SELinux targeted policy. blocks CWE-280
Oracle Linux 9 (1 partial rule)
- V-271452 OL 9 must use a Linux Security Module configured to enforce limits on system services. blocks CWE-280
RHEL 9 (2 partial rules)
- V-258078 RHEL 9 must use a Linux Security Module configured to enforce limits on system services. blocks CWE-280
- V-272496 RHEL 9 must elevate the SELinux context when an administrator calls the sudo command. blocks CWE-280