dbcve.org
Enterprise LinuxOperating system · Redhat

CVE-2026-26103

HIGH · 7.1 CVSS v3.1 Published 2026-02-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A flaw was found in the udisks storage management daemon that exposes a privileged D-Bus API for restoring LUKS encryption headers without proper authorization checks. The issue allows a local unprivileged user to instruct the root-owned udisks daemon to overwrite encryption metadata on block devices. This can permanently invalidate encryption keys and render encrypted volumes inaccessible. Successful exploitation results in a denial-of-service condition through irreversible data loss.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The udisks storage management daemon exposes a privileged D-Bus API for restoring LUKS encryption headers without proper authorization checks, allowing local unprivileged users to instruct the root-owned udisks daemon to overwrite encryption metadata on block devices, permanently invalidating encryption keys and causing irreversible data loss.

MitigationImplement proper authorization checks on the LUKS header restoration D-Bus API, restrict access to the udisks D-Bus interface via polkit or D-Bus policy configuration, or upgrade to a patched version of udisks when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Enterprise LinuxOperating system
Affected:= 10.0
UdisksApplication
Affected:= 2.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify udisks daemon is installed and identify its version
    Run 'rpm -qa | grep -i udisks' on RHEL or 'dpkg -l | grep -i udisks' on Debian-based systems. Check the package version returned (e.g., udisks2, udisks).
    Affected if The installed version of udisks matches version 2.0.0 (Freedesktop) or 10.0 (RHEL), or falls within the affected range.
  2. Confirm udisks daemon is running
    Run 'systemctl status udisks2' or 'ps aux | grep udisks' to check if the udisks daemon process is active.
    Affected if The udisks daemon is running, exposing the vulnerable D-Bus interface.
  3. Check D-Bus policy configuration for udisks
    Examine /etc/dbus-1/system.d/*udisks*.conf or /usr/share/dbus-1/system.d/*udisks*.conf files. Look for policy entries related to 'RestoreLUKSHeader' or 'LuksResume' methods.
    Affected if The D-Bus policy allows unauthenticated or unprivileged users to invoke LUKS header restoration methods, or no explicit restriction is found.
  4. Inspect polkit authorization for LUKS operations
    Check /etc/polkit-1/localauthority/10-vendor.d/ or run 'pkaction | grep -i luks' to list polkit actions related to LUKS operations.
    Affected if Polkit rules permit unprivileged users to perform LUKS header operations without authentication.
  5. Identify exposed LUKS encrypted devices via udisks
    Run 'udisksctl status' or 'lsblk -f' to list block devices with LUKS encryption that are visible to the udisks service.
    Affected if LUKS-encrypted devices are exposed through udisks and the D-Bus interface is accessible to the local user.

A system is affected if it runs udisks version 2.0.0 or RHEL 10.0 with the D-Bus interface accessible to unprivileged users and LUKS-encrypted devices exposed, allowing unauthorized LUKS header restoration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks on the LUKS header restoration D-Bus API, restrict access to the udisks D-Bus interface via polkit or D-Bus policy configuration, or upgrade to a patched version of udisks when available.

Fix this in Enterprise Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26103 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-26103 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data