CVE-2026-46054 is an improper access-control vulnerability in Linux kernel SELinux handling of OverlayFS files. The OverlayFS SELinux model requires that the current task be authorized to access the top-level user file and that the OverlayFS mounter's credentials authorize access to the lower-level backing file. Prior to the fix, mmap() and mprotect() operations did not correctly enforce the required backing-file checks. The correction invokes the security_mmap_backing_file() LSM hook for mmap() and uses the backing-file API with new LSM state to enforce the corresponding mprotect() checks.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel SELinux flaw involving inadequate OverlayFS access checks for mmap() and mprotect().
A Linux kernel SELinux vulnerability involving incorrect overlayfs mmap() and mprotect() access checks.
A Linux kernel SELinux/overlayfs vulnerability involving incorrect mmap() and mprotect() access checks.
A Linux kernel SELinux vulnerability involving incorrect overlayfs mmap() and mprotect() access checks.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.