CVE-2026-99789

Description

A flaw was found in the Linux kernel's block subsystem. When processing direct input/output (I/O) operations with misaligned memory buffers, the kernel rejects the operation but fails to restore the buffer tracking iterator to its original state. A local attacker can exploit this flaw by issuing specially crafted write requests, which triggers an out-of-bounds memory read when the system falls back to buffered I/O. This flaw primarily leads to a system crash, resulting in a Denial of Service (DoS), and may potentially expose sensitive kernel memory.

Statement

This vulnerability is rated Moderate severity because exploitation requires local user access and is limited to causing a denial of service via a kernel crash, without direct risk of data confidentiality exposure or arbitrary code execution. In standard Red Hat Enterprise Linux deployments, local users can trigger direct I/O operations through regular file system interfaces. While crafted vectored write requests can cause an out-of-bounds read during fallback to buffered I/O, the impact is strictly confined to host availability.

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/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/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:L/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.

Confidentiality

Technical Impact: Bypass Protection Mechanism

Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.

Other

Technical Impact: Varies by Context

The read operation could produce other undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.