Bug 2370051 (CVE-2025-6019)
| Summary: | CVE-2025-6019 libblockdev: LPE from allow_active to root in libblockdev via udisks | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | OSIDB Bzimport <bzimport> |
| Component: | vulnerability | Assignee: | Product Security DevOps Team <prodsec-dev> |
| Status: | NEW --- | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | unspecified | CC: | aph, fabian.kose, frans.postma, jaeshin, jwright, klaas, kyoshida, mhhall3, michael.h.hall-1, mpoole, security-response-team, spanjikk |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | --- | |
| Doc Text: |
A Local Privilege Escalation (LPE) vulnerability was found in libblockdev. Generally, the "allow_active" setting in Polkit permits a physically present user to take certain actions based on the session type. Due to the way libblockdev interacts with the udisks daemon, an "allow_active" user on a system may be able escalate to full root privileges on the target host. Normally, udisks mounts user-provided filesystem images with security flags like nosuid and nodev to prevent privilege escalation. However, a local attacker can create a specially crafted XFS image containing a SUID-root shell, then trick udisks into resizing it. This mounts their malicious filesystem with root privileges, allowing them to execute their SUID-root shell and gain complete control of the system.
|
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: | |||
| Bug Depends On: | 2373715 | ||
| Bug Blocks: | |||
| Deadline: | 2025-06-17 | ||
|
Description
OSIDB Bzimport
2025-06-03 16:06:11 UTC
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support Via RHSA-2025:9321 https://access.redhat.com/errata/RHSA-2025:9321 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions Via RHSA-2025:9324 https://access.redhat.com/errata/RHSA-2025:9324 This issue has been addressed in the following products: Red Hat Enterprise Linux 8.2 Advanced Update Support Via RHSA-2025:9320 https://access.redhat.com/errata/RHSA-2025:9320 This issue has been addressed in the following products: Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions Via RHSA-2025:9323 https://access.redhat.com/errata/RHSA-2025:9323 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions Via RHSA-2025:9325 https://access.redhat.com/errata/RHSA-2025:9325 This issue has been addressed in the following products: Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support Red Hat Enterprise Linux 8.6 Telecommunications Update Service Via RHSA-2025:9322 https://access.redhat.com/errata/RHSA-2025:9322 This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2025:9328 https://access.redhat.com/errata/RHSA-2025:9328 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.4 Extended Update Support Via RHSA-2025:9326 https://access.redhat.com/errata/RHSA-2025:9326 This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2025:9327 https://access.redhat.com/errata/RHSA-2025:9327 Hi, you seem to have forgotten the normal "Red Hat Enterprise Linux 8" release. I only see the ones for specific minor versions This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2025:9878 https://access.redhat.com/errata/RHSA-2025:9878 |