/

CVE-2026-26103

Severity:

HIGH RISK

(7.1)

Authorization Bypass / Missing Authorization in udisks LUKS

CVE-2026-26103

Modified

Vulnerability type

Category:

Authorization Bypass / Missing Authorization

CWE:

CWE-862

Impact:

Local Denial of Service via Irreversible Data Loss

Severity:

HIGH RISK

(7.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A missing authorization check in the udisks storage management daemon exposes a privileged D-Bus method that can restore (and thus overwrite) LUKS encryption headers on block devices on behalf of unprivileged users.

A local attacker who can call this D-Bus interface may corrupt the encryption metadata, invalidating keys and causing irreversible loss of access to encrypted volumes, resulting in a denial-of-service condition.

Affected context

This vulnerability affects systems running the udisks storage management daemon where:

  • The root-owned daemon exposes a D-Bus API for LUKS header restoration.
  • Invocations of this API are not correctly gated by authorization policies (e.g., polkit or equivalent).
  • Local, unprivileged users or processes are able to reach and invoke the affected D-Bus method.

It is most relevant on multi-user systems or environments where untrusted code can run locally and interact with system D-Bus services.

Exploit preconditions

  • Attack surface: Local system D-Bus interface exposed by the udisks daemon.
  • Required access: Ability to execute code or commands as an unprivileged local user on the target system.
  • Trigger point: Invoking the udisks D-Bus method responsible for restoring LUKS headers on a chosen block device.
  • Why exploitation is possible: The privileged operation is bound to a D-Bus API that either lacks an authorization check or applies insufficient policy, allowing untrusted callers to request destructive metadata overwrites without proof of administrative intent.

Why this happens

The core issue is a missing or incomplete authorization check around a privileged storage-management operation, mapping directly to CWE-862: Missing Authorization.

The udisks daemon exposes a method that can restore LUKS headers, an operation that inherently requires elevated privileges due to its destructive impact on encryption metadata.

Instead of enforcing a strong policy (for example, explicit administrative authorization per device and operation), the daemon trusts that any caller allowed onto the D-Bus can legitimately request header restoration.

This design flaw breaks the expected privilege boundary: an unprivileged user can trigger a high-impact operation in a root-owned service without additional verification.

Potential impact

  • Permanent invalidation of LUKS encryption headers on targeted block devices.
  • Loss of access to data on affected encrypted volumes, potentially without any recovery path.
  • Targeted denial-of-service against other local users by destroying their encrypted data volumes.
  • Disruption of system services that rely on encrypted partitions, such as home directories or application data stores.
  • Increased risk of operational outages in shared or multi-tenant environments where encrypted storage is critical.

General mitigation guidance

Mitigation should focus on restoring proper authorization and hardening access to destructive storage operations:

  • Ensure all privileged udisks D-Bus methods that modify disk structures or encryption metadata are protected by strong authorization checks, such as explicit administrator approval via a policy engine.
  • Treat operations that alter LUKS headers and partition metadata as high-risk, requiring interactive or policy-based confirmation rather than silent acceptance from arbitrary D-Bus clients.
  • Constrain which users and services may access the system D-Bus interfaces that expose storage-management APIs; consider using separate buses or stricter policies for administrative services.
  • Apply the principle of least privilege within the daemon code paths, limiting the scope and capabilities of methods that can be invoked by general users.
  • Incorporate defense-in-depth controls such as logging and rate-limiting for destructive actions on storage devices to reduce the window for abuse and support incident response.

How teams detect issues like this

Detection is best approached by inspecting both code and system behavior:

  • Use static analysis or manual code review to identify D-Bus methods in udisks (and similar daemons) that perform privileged operations without explicit authorization checks or policy lookups.
  • Review D-Bus introspection data and policy files to confirm that methods capable of altering disk structures, LUKS headers, or partition tables are restricted to privileged users or roles.
  • Monitor system logs for unexpected LUKS header restoration attempts, unusual storage errors, or repeated failures to mount encrypted volumes that could indicate metadata corruption.
  • Employ configuration and policy compliance checks in CI/CD or system-hardening tools to flag services that expose destructive operations over D-Bus without adequate access control definitions.

Sources

SourceLink
access.redhat.comaccess.redhat.com/errata/RHSA-2026:3476
access.redhat.comaccess.redhat.com/errata/RHSA-2026:5831
access.redhat.comaccess.redhat.com/security/cve/CVE-2026-26103
bugzilla.redhat.combugzilla.redhat.com/show_bug.cgi?id=2433719
github.comgithub.com/storaged-project/udisks/security/advisories/GHSA-c75h-phf8-ccjm
security.access.redhat.comsecurity.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-26103.json

Frequently asked

questions

No, the issue is tied to local inter-process communication. Exploitation requires the attacker to run code or commands as a local user on the system that hosts the vulnerable udisks daemon.

No administrative privileges are required if the vulnerable D-Bus method is callable by unprivileged users. The flaw specifically arises because the root-owned daemon performs a privileged operation on behalf of an untrusted caller without proper authorization.

The safest fix pattern is to enforce strict authorization on all D-Bus methods that alter disk or encryption metadata, ensuring that only authenticated and authorized administrators can invoke them. This typically involves integrating or correcting policy checks within the daemon before performing any destructive operation.

To prevent similar problems, treat every privileged IPC endpoint as a critical security boundary: require explicit authorization checks for destructive operations, subject new APIs to security review, define clear D-Bus or IPC policies that restrict access by default, and integrate automated checks that flag newly introduced methods lacking access control.

Find out what's already
exploitable in your codebase.