CVE-2026-89573

Description

A flaw was found in the Linux kernel's device mapper (dm) array component. A local attacker could exploit this vulnerability by providing specially crafted metadata. This crafted metadata causes the system to misinterpret the size of data blocks, leading to an out-of-bounds read. This memory corruption could result in system instability or a denial of service.

Statement

A flaw of moderate severity was found in the Linux kernel's device-mapper (dm) array metadata handling, as used by dm-cache. The array block validity check (array_block_check()) only compares a block's header against itself, so a metadata block whose value size disagrees with the value size expected by the caller is accepted as internally consistent. If the dm-cache mappings root in the superblock points at a hint array block holding 4-byte entries and is loaded through an info expecting 8-byte entries, element_at() strides 8 bytes over 4-byte entries and reads past the end of the 4096-byte block, causing an out-of-bounds read that can result in kernel memory corruption, system instability, or a denial of service. Exploitation requires a local attacker able to supply specially crafted device-mapper metadata; dm arrays only read their own blocks, so this is triggered only by crafted metadata rather than by normal operation. Red Hat rated this flaw MODERATE (CVSS 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) because the out-of-bounds access primarily affects availability; this differs from the upstream CVEORG score of 7.8, which assumes high confidentiality and integrity impacts that Red Hat's analysis does not support. Affected Red Hat Enterprise Linux kernel and kernel-rt streams and OpenShift Container Platform (RHCOS) releases are resolved as deferred: because the impact is MODERATE with a CVSS score below 7.0, the fix is deferred to a future scheduled update rather than addressed urgently, leaving a residual risk of local denial of service from crafted dm metadata.

Mitigation

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.

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).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.5N/A7.8
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

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

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

Understanding the Weakness (CWE)

Other

Technical Impact: Varies by Context

When the product accesses the resource using an incompatible type, this could trigger logical errors because the resource does not have expected properties.

Availability,Integrity,Confidentiality

Technical Impact: Read Memory; Modify Memory; Execute Unauthorized Code or Commands; DoS: Crash, Exit, or Restart

If a memory buffer is accessed using an incompatible type, and the allocated buffer is smaller than the type that the code is attempting to access, then an attacker could read or write memory outside the bounds of the buffer, leading to a crash or possibly code execution.

Frequently Asked Questions

Want to get errata notifications? Sign up here.