CVE-2025-6019: Libblockdev: lpe from allow_active to root in libblockdev via udisks
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.
Security readout for executives and security teams
CVE-2025-6019 is a local privilege escalation flaw in libblockdev when used through udisks. A user who already has local access and an active session may be able to move from limited privileges to full root control. This is not a remote internet bug, but it matters on shared Linux systems, workstations, and servers with untrusted local users. Structured affected data names Red Hat Enterprise Linux 7 ELS, 8, 9, 10, and several AUS/EUS/E4S/TUS/SAP channels with affected libblockdev builds. Other referenced distribution advisories should be checked directly. Exposure requires local access and relevant udisks/libblockdev functionality, so prioritize multi-user Linux hosts and managed workstations. Patch on a high-priority operational cycle, especially for shared Linux servers, jump hosts, developer workstations, and environments where low-privilege local access is plausible. The main business risk is that a minor local foothold could become full host compromise. Mitigation focus: Apply vendor-provided libblockdev and udisks updates for affected distributions.; Review Red Hat errata matching each RHEL channel in use.; Check Debian, SUSE, and other distro advisories for package-specific status..
Prepared
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-250: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
5Timeline events
2ADP providers
18Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.