CVE-2025-11568

Description

A data corruption vulnerability has been identified in the luksmeta utility when used with the LUKS1 disk encryption format. An attacker with the necessary permissions can exploit this flaw by writing a large amount of metadata to an encrypted device. The utility fails to correctly validate the available space, causing the metadata to overwrite and corrupt the user's encrypted data. This action leads to a permanent loss of the stored information. Devices using the LUKS formats other than LUKS1 are not affected by this issue.

Statement

This vulnerability has been rated as having the impact of 'Moderate' by the Red Hat Product Security team. This happens because for an successful attack to take place, the attacker needs to have root privileges to me able to run luksmeta. It worth to notice this vulnerability only affects luksmeta when it's being used over a encrypted partition with LUKS1 versio, further LUKS versions are not vulnerable to this. While LUKS1 is not the default LUKS version in Red Hat Enterprise Linux since Red Hat Enterprise Linux 8, LUKS1 is still supported.

Mitigation

There's no available mitigation for this vulnerability.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score4.4N/A4.4
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredHighN/AHigh
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/ANone
Integrity ImpactHighN/AHigh
Availability ImpactNoneN/ANone

Vector

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

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

Understanding the Weakness (CWE)

Other,Integrity,Availability

Technical Impact: Varies by Context; DoS: Resource Consumption (CPU); Modify Memory; Read Memory

When the quantity is not properly validated, then attackers can specify malicious quantities to cause excessive resource allocation, trigger unexpected failures, enable buffer overflows, etc.

Frequently Asked Questions

Want to get errata notifications? Sign up here.