Skip to content
Noroxi
NVD / CVE Program· CNA redhat

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

Noroxi assessment

Priority: Monitor (action score 34/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.65% (FIRST EPSS); higher than 51.2% of all records.
  • Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: storaged-project udisks 2.10.2, 2.10.91.

Low priority for now. Upgrade to storaged-project udisks 2.10.2, 2.10.91 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 8.5 · v3.1—Proof of concept Fix available
Published
Aug 28, 2025
Updated
Sep 25, 2026
EPSS
0.6% · 51th percentile

Report tools

JSON

Action score

34

Monitor

Low priority for now.

CVSS
34 / 40 · 8.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.6%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · redhat
8.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-8067

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • Red Hat Red Hat Enterprise Linux 10

    • 0:2.10.90-5.el10_0.1 and laternot affected · rpm
  • Red Hat Red Hat Enterprise Linux 6

    • all versionsunknown
  • Red Hat Red Hat Enterprise Linux 7 Extended Lifecycle Support

    • 0:2.8.4-1.el7_9.2 and laternot affected · rpm
  • Red Hat Red Hat Enterprise Linux 8

    • 0:2.9.0-16.el8_10.1 and laternot affected · rpm
  • Red Hat Red Hat Enterprise Linux 8.2 Advanced Update Support

    • 0:2.8.3-2.el8_2.1 and laternot affected · rpm
  • Red Hat Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support

    • 0:2.9.0-6.el8_4.1 and laternot affected · rpm
  • Red Hat Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On

    • 0:2.9.0-6.el8_4.1 and laternot affected · rpm
  • Red Hat Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support

    • 0:2.9.0-9.el8_6.1 and laternot affected · rpm
  • Red Hat Red Hat Enterprise Linux 8.6 Telecommunications Update Service

    • 0:2.9.0-9.el8_6.1 and laternot affected · rpm
  • Red Hat Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions

    • 0:2.9.0-9.el8_6.1 and laternot affected · rpm
  • Red Hat Red Hat Enterprise Linux 8.8 Telecommunications Update Service

    • 0:2.9.0-13.el8_8.1 and laternot affected · rpm
  • Red Hat Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions

    • 0:2.9.0-13.el8_8.1 and laternot affected · rpm

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10libudisks2before 2.10.90-5.el10_0.12.10.90-5.el10_0.1
AlmaLinux:10libudisks2-develbefore 2.10.90-5.el10_0.12.10.90-5.el10_0.1
AlmaLinux:10udisks2before 2.10.90-5.el10_0.12.10.90-5.el10_0.1
AlmaLinux:10udisks2-iscsibefore 2.10.90-5.el10_0.12.10.90-5.el10_0.1
AlmaLinux:10udisks2-lsmbefore 2.10.90-5.el10_0.12.10.90-5.el10_0.1
AlmaLinux:10udisks2-lvm2before 2.10.90-5.el10_0.12.10.90-5.el10_0.1
AlmaLinux:8libudisks2before 2.9.0-16.el8_10.12.9.0-16.el8_10.1
AlmaLinux:8libudisks2-develbefore 2.9.0-16.el8_10.12.9.0-16.el8_10.1
AlmaLinux:8udisks2before 2.9.0-16.el8_10.12.9.0-16.el8_10.1
AlmaLinux:8udisks2-iscsibefore 2.9.0-16.el8_10.12.9.0-16.el8_10.1
AlmaLinux:8udisks2-lsmbefore 2.9.0-16.el8_10.12.9.0-16.el8_10.1
AlmaLinux:8udisks2-lvm2before 2.9.0-16.el8_10.12.9.0-16.el8_10.1
AlmaLinux:9libudisks2before 2.9.4-11.el9_6.12.9.4-11.el9_6.1
AlmaLinux:9libudisks2-develbefore 2.9.4-11.el9_6.12.9.4-11.el9_6.1
AlmaLinux:9udisks2before 2.9.4-11.el9_6.12.9.4-11.el9_6.1
AlmaLinux:9udisks2-iscsibefore 2.9.4-11.el9_6.12.9.4-11.el9_6.1
AlmaLinux:9udisks2-lsmbefore 2.9.4-11.el9_6.12.9.4-11.el9_6.1
AlmaLinux:9udisks2-lvm2before 2.9.4-11.el9_6.12.9.4-11.el9_6.1
Debian:11udisks2before 2.9.2-2+deb11u32.9.2-2+deb11u3
Debian:12udisks2before 2.9.4-4+deb12u22.9.4-4+deb12u2
Debian:13udisks2before 2.10.1-12.1+deb13u12.10.1-12.1+deb13u1
Debian:14udisks2before 2.10.90-3.12.10.90-3.1
openSUSE:Leap 15.6udisks2before 2.9.2-150400.3.11.12.9.2-150400.3.11.1
openSUSE:Leap 16.0udisks2before 2.10.1-160000.3.12.10.1-160000.3.1

+96

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
storaged-project udisks2.10.2Vendor (CNA)
storaged-project udisks2.10.91Vendor (CNA)
almalinux:libudisks22.9.0-16.el8_10.1 · AlmaLinux:8Package registry (OSV)
almalinux:libudisks2-devel2.9.0-16.el8_10.1 · AlmaLinux:8Package registry (OSV)
almalinux:udisks22.9.0-16.el8_10.1 · AlmaLinux:8Package registry (OSV)
almalinux:udisks2-iscsi2.9.0-16.el8_10.1 · AlmaLinux:8Package registry (OSV)
almalinux:udisks2-lsm2.9.0-16.el8_10.1 · AlmaLinux:8Package registry (OSV)
almalinux:udisks2-lvm22.9.0-16.el8_10.1 · AlmaLinux:8Package registry (OSV)
debian:udisks22.9.4-4+deb12u2 · Debian:12Package registry (OSV)
opensuse:udisks22.9.2-150400.3.11.1 · openSUSE:Leap 15.6Package registry (OSV)
red hat:libudisks20:2.9.0-16.el8_10.1 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:libudisks2-debuginfo0:2.9.0-16.el8_10.1 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:libudisks2-devel0:2.9.0-16.el8_10.1 · Red Hat:enterprise_linux:8::crbPackage registry (OSV)
red hat:udisks20:2.9.0-16.el8_10.1 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:udisks2-debuginfo0:2.9.0-16.el8_10.1 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:udisks2-debugsource0:2.9.0-16.el8_10.1 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:udisks2-iscsi0:2.9.0-16.el8_10.1 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:udisks2-iscsi-debuginfo0:2.9.0-16.el8_10.1 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:udisks2-lsm0:2.9.0-16.el8_10.1 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:udisks2-lsm-debuginfo0:2.9.0-16.el8_10.1 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:udisks2-lvm20:2.9.0-16.el8_10.1 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:udisks2-lvm2-debuginfo0:2.9.0-16.el8_10.1 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
rocky linux:udisks20:2.9.0-16.el8_10.1 · Rocky Linux:8Package registry (OSV)
suse:udisks22.1.3-3.11.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:udisks22.9.2-150400.3.11.1 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02025-09-04

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+7 d
  3. TodayNov 1, 2026+430 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality impact
Low
Integrity impact
Low
Availability impact
High

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records