CVE-2025-6019 Libblockdev: lpe from allow_active to root in libblockdev via udisks

High 7.0 Published Updated

A local attacker can escalate to root privileges by tricking udisks into mounting a malicious XFS image with SUID binaries via libblockdev.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2025-6019?

CVE-2025-6019 is a high-severity vulnerability in Red Hat Enterprise Linux 10, published on 19 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

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.

Weakness: CWE-250

Which versions are affected by CVE-2025-6019?

Linux distribution packages (40)
libblockdev AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev AlmaLinux:10All versions3.2.0-4.el10_0
libblockdev-crypto AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev-crypto AlmaLinux:10All versions3.2.0-4.el10_0
libblockdev-crypto-devel AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev-devel AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev-dm AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev-dm AlmaLinux:10All versions3.2.0-4.el10_0
libblockdev-dm-devel AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev-fs AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev-fs AlmaLinux:10All versions3.2.0-4.el10_0
libblockdev-fs-devel AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev-loop AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev-loop AlmaLinux:10All versions3.2.0-4.el10_0
libblockdev-loop-devel AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev-lvm AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev-lvm AlmaLinux:10All versions3.2.0-4.el10_0
libblockdev-lvm-dbus AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev-lvm-dbus AlmaLinux:10All versions3.2.0-4.el10_0
libblockdev-lvm-dbus-devel AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev-lvm-devel AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev-mdraid AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev-mdraid AlmaLinux:10All versions3.2.0-4.el10_0
libblockdev-mdraid-devel AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev-mpath AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev-mpath AlmaLinux:10All versions3.2.0-4.el10_0
libblockdev-mpath-devel AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev-nvdimm AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev-nvdimm AlmaLinux:10All versions3.2.0-4.el10_0
libblockdev-nvdimm-devel AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev-nvme AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev-nvme AlmaLinux:10All versions3.2.0-4.el10_0
libblockdev-nvme-devel AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev-part AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev-part AlmaLinux:10All versions3.2.0-4.el10_0
libblockdev-part-devel AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev-plugins-all AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev-plugins-all AlmaLinux:10All versions3.2.0-4.el10_0
libblockdev-s390 AlmaLinux:10All versions3.2.0-3.el10_0.alma.1
libblockdev-s390 AlmaLinux:10All versions3.2.0-4.el10_0

How do I fix CVE-2025-6019?

Apply the vendor's patch.

Is CVE-2025-6019 being exploited?

There is no known exploitation of CVE-2025-6019 in the wild and no public exploit code.

Public exploit code: 11 proofs of concept on GitHub.

Sources

Also known as ALSA-2025:9327, ALSA-2025:9328, ALSA-2025:9878, ALSA-2025:A004, ALSA-2025:A005, ALSA-2025:A006 and 37 more.

Is CVE-2025-6019 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free