CVE-2025-6019

Source
https://nvd.nist.gov/vuln/detail/CVE-2025-6019
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-6019.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2025-6019
Downstream
Related
Published
2025-06-19T12:15:19Z
Modified
2025-07-29T11:21:00.847716Z
Summary
[none]
Details

A Local Privilege Escalation (LPE) vulnerability was found in libblockdev. Generally, the "allowactive" 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 "allowactive" 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.

References

Affected packages

Debian:11 / libblockdev

Package

Name
libblockdev
Purl
pkg:deb/debian/libblockdev?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
2.25-2+deb11u1

Affected versions

2.*

2.25-2

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:12 / libblockdev

Package

Name
libblockdev
Purl
pkg:deb/debian/libblockdev?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
2.28-2+deb12u1

Affected versions

2.*

2.28-2

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:13 / libblockdev

Package

Name
libblockdev
Purl
pkg:deb/debian/libblockdev?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
3.3.0-2.1

Ecosystem specific

{
    "urgency": "not yet assigned"
}