CVE-2026-111555
Received Received - Intake

Improper Boundary Validation in luksmeta Leads to Data Corruption

Publication date: 2026-10-16

Last updated on: 2026-10-16

Assigner: redhat-SADP

Description
A flaw was found in luksmeta. Improper boundary validation of metadata slots allows an attacker capable of supplying or modifying a disk header to redirect wipe or load operations outside the intended metadata area. An attacker could exploit this vulnerability by providing a crafted header with valid checksums to overwrite or zero out encrypted payload data, resulting in persistent data loss and corrupted storage. Exploitation typically requires privileged access to modify raw block devices or the ability to induce an administrator to process an untrusted disk image.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-16
Last Modified
2026-10-16
Generated
2026-10-16
AI Q&A
2026-10-16
EPSS Evaluated
N/A
NVD
CVE-2026-111555
EUVD
EUVD-2026-102857

Affected Vendors & Products

Showing 5 associated CPEs
Vendor Product Version / Range
Red Hat Red Hat Enterprise Linux 10 *
Red Hat Red Hat Enterprise Linux 7 *
Red Hat Red Hat Enterprise Linux 8 *
Red Hat Red Hat Enterprise Linux 9 *
Red Hat Red Hat OpenShift Container Platform 4 *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-1285 The product receives input that is expected to specify an index, position, or offset into an indexable resource such as a buffer or file, but it does not validate or incorrectly validates that the specified index/position/offset has the required properties.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is in luksmeta, a tool for managing LUKS metadata. It involves improper validation of metadata slots, allowing an attacker to redirect wipe or load operations outside the intended metadata area. By providing a crafted disk header with valid checksums, an attacker can overwrite or zero out encrypted payload data, causing persistent data loss and storage corruption.

Detection Guidance

Detection requires checking for luksmeta usage and validating disk headers. Inspect luksmeta operations on LUKS1 devices using commands like 'luksmeta show /dev/sdX' or 'strace luksmeta load /dev/sdX 0' to observe header interactions. Review system logs for unauthorized disk modifications or luksmeta processes. Ensure metadata slot ranges are within expected bounds.

Impact Analysis

This vulnerability can lead to persistent data loss and corrupted storage. An attacker with privileged access could overwrite encrypted payload data, making filesystems inaccessible. Exploitation typically requires root access or tricking an administrator into processing an untrusted disk image.

Compliance Impact

This vulnerability primarily causes persistent data loss and storage corruption by allowing overwrite of encrypted payload data. While it does not directly expose confidential data, data loss could violate GDPR's integrity principle or HIPAA's availability requirements for protected health information. Compliance impact depends on whether affected systems store regulated data and the extent of corruption.

Mitigation Strategies

Immediate mitigation involves avoiding untrusted disk images or headers. Do not process raw disk images from untrusted sources. Restrict raw block device access to trusted administrators only. Monitor for suspicious luksmeta operations. Upgrade to supported versions if fixes become available. Consult Red Hat support for guidance if affected.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-111555. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart