CVE-2026-90396

Description

A flaw was found in the Linux kernel's block direct I/O (DIO) subsystem. When an integrity mapping fails during direct I/O operations, a reference to the direct I/O resource is not properly released. This resource leak could potentially be exploited by a local attacker, leading to a denial of service (DoS) due to resource exhaustion over time.

Statement

This vulnerability is rated as Low severity because triggering the resource leak requires local access and depends on uncommon direct I/O metadata mapping failures to cause gradual memory exhaustion. The issue is confined to error-handling paths within the kernel block subsystem and does not permit privilege escalation or compromise system confidentiality or integrity. Exploiting the flaw requires sustained local I/O activity under specific error conditions, significantly limiting practical risk in standard enterprise deployments.

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)

Availability

Technical Impact: DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)

If an adversary can prevent a reference count from reaching zero, then resources might not be released when they are supposed to, thus causing resources to become scarce for future needs.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If an adversary can cause a reference count to reach zero when the resource is still in use, then a resource might be released before it is supposed to be, possibly forcing an error that causes the product to crash or exit out of its current operation.

Frequently Asked Questions

Want to get errata notifications? Sign up here.