---
id: CVE-2026-111555
title: 'Luksmeta: missing slot-range validation permits out-of-gap device i/o'
summary: >-
  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
  exp…
severity: medium
cvss: 6
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H'
cvssSource: cna
cwe:
  - CWE-1285
vendor: Red Hat
product: luksmeta
affected:
  - luksmeta (all versions)
  - luksmeta (all versions)
  - luksmeta (all versions)
  - luksmeta (all versions)
  - openshift/ose-rhel-coreos-8 (all versions)
  - openshift/ose-rhel-coreos-9 (all versions)
published: '2026-10-16'
updated: '2026-10-16'
sourceUpdated: '2026-10-16T12:19:44.320Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-111555'
references:
  - url: 'https://access.redhat.com/security/cve/CVE-2026-111555'
  - url: 'https://bugzilla.redhat.com/show_bug.cgi?id=2554026'
    label: RHBZ#2554026
tags:
  - cve.org
ingestedAt: '2026-10-16T13:06:42.676Z'
---

## Overview

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.

## Affected

- `luksmeta (all versions)`
- `luksmeta (all versions)`
- `luksmeta (all versions)`
- `luksmeta (all versions)`
- `openshift/ose-rhel-coreos-8 (all versions)`
- `openshift/ose-rhel-coreos-9 (all versions)`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.

### Workarounds

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.