CVE-2026-99596

Description

A flaw was found in the Linux kernel's NVMe (Non-Volatile Memory Express) driver. A local user with access to NVMe device commands could exploit a race condition during controller removal while input/output operations are actively pending. Because the driver moves namespace entries onto the local stack without properly waiting for active reader processes to finish, the kernel may reference invalid stack memory, resulting in an out-of-bounds read, a system crash, and a Denial of Service (DoS).

Statement

This vulnerability is rated as having a Moderate impact because exploitation requires elevated administrative privileges to trigger controller teardown or manipulate NVMe devices while concurrent operations are pending, and the resulting blast radius is confined to a local denial of service. Standard unprivileged users cannot issue the administrative commands necessary to disconnect controllers or execute low-level passthrough operations. In typical Red Hat Enterprise Linux deployments, NVMe storage devices are managed exclusively by trusted root administrators, preventing unauthorized users from triggering the race condition.

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 Score4.4N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredHighN/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:H/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Integrity,Other

Technical Impact: Alter Execution Logic; Unexpected State

The main problem is that -- if a lock is overcome -- data could be altered in a bad state.

Frequently Asked Questions

Want to get errata notifications? Sign up here.