Bug 2482025 (CVE-2026-46054)
| Summary: | CVE-2026-46054 kernel: selinux: fix overlayfs mmap() and mprotect() access checks | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | OSIDB Bzimport <bzimport> |
| Component: | vulnerability | Assignee: | Product Security <prodsec-ir-bot> |
| Status: | NEW --- | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | unspecified | CC: | rhel-process-autobot, watson-tool-maintainers |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | --- | |
| Doc Text: |
A flaw was found in the Linux kernel's SELinux security module when handling overlayfs. The existing security model for overlayfs does not properly enforce access controls for `mmap()` and `mprotect()` operations. This oversight could allow a local attacker to bypass intended security policies, potentially leading to unauthorized access to files within an overlayfs filesystem. The vulnerability is resolved by enhancing backing file enforcement for `mmap()` and leveraging new LSM (Linux Security Module) capabilities for `mprotect()` access controls.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
OSIDB Bzimport
2026-05-27 15:07:38 UTC
Upstream advisory: https://lore.kernel.org/linux-cve-announce/2026052754-CVE-2026-46054-b185@gregkh/T This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:25191 https://access.redhat.com/errata/RHSA-2026:25191 This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2026:27812 https://access.redhat.com/errata/RHSA-2026:27812 This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2026:27811 https://access.redhat.com/errata/RHSA-2026:27811 This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:30848 https://access.redhat.com/errata/RHSA-2026:30848 |