CVE-2026-98635

Description

A flaw was found in the Linux kernel. An attacker who attaches a specially crafted storage device can cause a Denial of Service (DoS) or kernel memory corruption. When the kernel revalidates zoned block devices—storage media divided into independent physical regions—it fails to verify that the reported zone index fits within the allocated memory buffer. This issue triggers an out-of-bounds write operation, leading to system instability or a kernel crash.

Statement

Red Hat has evaluated this vulnerability as a Moderate severity impact because successful exploitation requires connecting a malicious or specially manipulated zoned block device, which demands physical presence or the ability to attach virtualized storage hardware. While the improper boundary validation during device inspection can induce kernel memory corruption and cause an immediate system crash, it cannot be triggered across the network without existing storage attachment capabilities. In typical Red Hat deployments, zoned storage architectures are rarely exposed to untrusted external media, significantly restricting potential attack vectors.

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 Score6.2N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredNoneN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

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

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory; Execute Unauthorized Code or Commands

Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.

Other

Technical Impact: Unexpected State

Subsequent write operations can produce undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.