CVE-2025-11568: Luksmeta: data corruption when handling luks1 partitions with luksmeta
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.
Security readout for executives and security teams
Plain-English summary
CVE-2025-11568 can cause permanent encrypted data loss when luksmeta is used with LUKS1 volumes. A user or process with high local privileges can write excessive metadata, and luksmeta may overwrite encrypted user data. This is not a remote takeover issue, but it is serious for systems relying on LUKS1 encrypted storage.
Executive priority
Treat as a targeted data-loss risk for encrypted storage operations, not an internet-scale emergency. Prioritize systems with LUKS1 and luksmeta, especially regulated or business-critical data stores where irreversible corruption would cause operational impact.
Technical view
The flaw is improper validation of available metadata space in luksmeta for LUKS1 partitions. CVSS is 4.4 with local access, low complexity, high privileges, no user interaction, and high integrity impact. Other LUKS formats are stated as unaffected. Red Hat lists affected RHEL and OpenShift/RHCOS package contexts.
Likely exposure
Exposure is most likely on Linux systems that have luksmeta installed and manage LUKS1 encrypted devices. The source bundle lists affected Red Hat Enterprise Linux 7, 8, 9, 10 and Red Hat OpenShift Container Platform 4/RHCOS contexts.
Exploitation context
No active exploitation is indicated; the CVE is not in KEV. Abuse requires local high privileges and interaction with an encrypted device. The practical risk is destructive data corruption rather than confidentiality loss or remote code execution.
Researcher notes
Key constraints are local access and high privileges. The affected condition is specifically luksmeta handling LUKS1 metadata space. The public bundle does not support claims of remote exploitation or broad compromise. Upstream pull request and Red Hat advisories should be reviewed for implementation details and fixed versions.
Mitigation direction
Identify systems with luksmeta installed and LUKS1 encrypted volumes.
Prioritize Red Hat systems listed as affected in the vendor advisories.
Apply applicable vendor security updates from referenced Red Hat advisories.
If updates are unavailable, follow vendor guidance before using luksmeta on LUKS1 devices.
Maintain verified backups for any LUKS1 volumes managed with luksmeta.
Validation and detection
Inventory luksmeta package presence and version across Linux fleets.
Confirm whether encrypted devices use LUKS1 versus other LUKS formats.
Map installed packages to affected Red Hat product versions.
Review Red Hat advisory status for fixed package availability.
Verify backups and recovery procedures for affected encrypted volumes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-1284: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-1284 · source CWE mapping
Improper Validation of Specified Quantity in Input
Improper Validation of Specified Quantity in Input represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.