# CVE-2025-6019: Libblockdev: lpe from allow_active to root in libblockdev via udisks > A local attacker can escalate to root privileges by tricking udisks into mounting a malicious XFS image with SUID binaries via libblockdev. - **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **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:** Yes - **Published:** 19 Jun 2025 - **Updated:** 30 Jun 2026 - **Also known as:** ALSA-2025:9327, ALSA-2025:9328, ALSA-2025:9878, ALSA-2025:A004, ALSA-2025:A005, ALSA-2025:A006, AZL-64187, AZL-64190, CLSA-2025-1753131177, CLSA-2025-1754340109, CLSA-2025-1764325063, CLSA-2026-1791302095, DEBIAN-CVE-2025-6019, DLA-4221-1, DSA-5943-1, GHSA-mpgj-hch9-5rvx, MGASA-2025-0188, OESA-2025-1677, OESA-2025-1688, RHSA-2025:10796, RHSA-2025:9320, RHSA-2025:9321, RHSA-2025:9322, RHSA-2025:9323, RHSA-2025:9324, RHSA-2025:9325, RHSA-2025:9326, RHSA-2025:9327, RHSA-2025:9328, RHSA-2025:9878, RLSA-2025:9327, RLSA-2025:9328, RLSA-2025:9878, SUSE-SU-2025:02043-1, SUSE-SU-2025:02044-1, SUSE-SU-2025:20426-1, SUSE-SU-2025:20440-1, UBUNTU-CVE-2025-6019, USN-7577-1, USN-7577-2, USN-7578-1, USN-7578-2, openSUSE-SU-2025:15237-1 ## 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 (Execution with Unnecessary Privileges) ## Which versions are affected by CVE-2025-6019? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libblockdev` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev` | AlmaLinux:10 | All versions | 3.2.0-4.el10_0 | | `libblockdev-crypto` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev-crypto` | AlmaLinux:10 | All versions | 3.2.0-4.el10_0 | | `libblockdev-crypto-devel` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev-devel` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev-dm` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev-dm` | AlmaLinux:10 | All versions | 3.2.0-4.el10_0 | | `libblockdev-dm-devel` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev-fs` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev-fs` | AlmaLinux:10 | All versions | 3.2.0-4.el10_0 | | `libblockdev-fs-devel` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev-loop` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev-loop` | AlmaLinux:10 | All versions | 3.2.0-4.el10_0 | | `libblockdev-loop-devel` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev-lvm` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev-lvm` | AlmaLinux:10 | All versions | 3.2.0-4.el10_0 | | `libblockdev-lvm-dbus` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev-lvm-dbus` | AlmaLinux:10 | All versions | 3.2.0-4.el10_0 | | `libblockdev-lvm-dbus-devel` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev-lvm-devel` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev-mdraid` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev-mdraid` | AlmaLinux:10 | All versions | 3.2.0-4.el10_0 | | `libblockdev-mdraid-devel` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev-mpath` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev-mpath` | AlmaLinux:10 | All versions | 3.2.0-4.el10_0 | | `libblockdev-mpath-devel` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev-nvdimm` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev-nvdimm` | AlmaLinux:10 | All versions | 3.2.0-4.el10_0 | | `libblockdev-nvdimm-devel` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev-nvme` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev-nvme` | AlmaLinux:10 | All versions | 3.2.0-4.el10_0 | | `libblockdev-nvme-devel` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev-part` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev-part` | AlmaLinux:10 | All versions | 3.2.0-4.el10_0 | | `libblockdev-part-devel` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev-plugins-all` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev-plugins-all` | AlmaLinux:10 | All versions | 3.2.0-4.el10_0 | | `libblockdev-s390` | AlmaLinux:10 | All versions | 3.2.0-3.el10_0.alma.1 | | `libblockdev-s390` | AlmaLinux:10 | All versions | 3.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: - https://github.com/guinea-offensive-security/CVE-2025-6019 (github_poc): https://github.com/guinea-offensive-security/CVE-2025-6019 - exploit (github_poc): https://github.com/And-oss/CVE-2025-6019-exploit - https://github.com/neko205-mx/CVE-2025-6019_Exploit (github_poc): https://github.com/neko205-mx/CVE-2025-6019_Exploit - CVE-2025-6019: udisks2 XFS Resize TOCTOU Privilege Escalation (github_poc): https://github.com/JM00NJ/CVE-2025-6019-udisks2-XFS-Resize-TOCTOU-Privilege-Escalation - Script-only privilege escalation chain using CVE-2025-6019 and UDisks2 (no filesystem image included). (github_poc): https://github.com/symphony2colour/CVE-2025-6019-udisks-lpe-no-image - Full BadUSB attack chain: keystroke-injection payload delivery, C2 client, privilege escalation (CVE-2025-6019), and systemd persistence on Linux. (github_poc): https://github.com/JustThinkingHard/HID-Attack ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-6019 and fix it if it is affected. What it is: 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. Exploitation: There is no known exploitation of CVE-2025-6019 in the wild and no public exploit code. Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-6019/ (Markdown: https://insights.sbomify.com/CVE-2025-6019/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-6019 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-6019 - OSV: https://osv.dev/vulnerability/CVE-2025-6019 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-6019/ Summaries are generated and may contain mistakes; the official description above is the record.