CVE-2026-97409

Description

A flaw was found in the Linux kernel's NVMe over Fibre Channel (NVMe-FC) driver. When establishing a connection to an NVMe-FC target, an administrative request timeout triggers error-handling routines that attempt to abort requests on uninitialized I/O queues. A malicious or unresponsive target could trigger this behavior during connection setup, leading to a kernel crash and a Denial of Service (DoS).

Statement

A moderate severity denial of service flaw was found in the Linux kernel's NVMe over Fibre Channel (NVMe-FC) driver. It affects the kernel and kernel-rt packages in Red Hat Enterprise Linux 8, 9, and 10 and the RHEL CoreOS kernels shipped with OpenShift 4 and 5. When a new NVMe-FC controller is in the CONNECTING state, an administrative request timeout schedules error-recovery work that aborts outstanding requests in both the admin and I/O tagsets. Because ctrl->queue_count is initialized early while the I/O tagset is not, the error handler can iterate over an I/O tagset that has not been created yet, producing kernel warnings (lockdep turning off the locking correctness validator) and potentially crashing the kernel. A malicious or unresponsive NVMe-FC target can trigger this behavior during connection setup, causing a denial of service. Red Hat rates this flaw Moderate because triggering it requires conditions on the local NVMe fabrics connection path and the impact is limited to availability; this is lower than the CVEORG score of 8.8 (Important), which assumes an unprivileged adjacent-network attacker with confidentiality and integrity impact that the current evidence does not demonstrate. Fixes for the affected Red Hat Enterprise Linux and OpenShift streams are currently deferred to future updates; the residual risk is limited to systems that use NVMe over Fibre Channel storage, where a failed or malicious target connection attempt could disrupt the host through the faulty error-recovery path. Red Hat Enterprise Linux 6 and 7 (including kernel-rt), RHEL 8.4, and the RHEL In-Vehicle OS (RHEL for Automotive) streams are marked not affected because the vulnerable code is not present.

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/A8.8
Attack VectorLocalN/AAdjacent Network
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ANone
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:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory; Read Application Data

When reusing a resource such as memory or a program variable, the original contents may not have been cleared before it is sent to an untrusted party.

Availability

Technical Impact: DoS: Crash, Exit, or Restart; DoS: Instability

The uninitialized resource may contain values that cause program flow to change in ways that the programmer did not intend, possibly leading to a crash.

Other

Technical Impact: Unexpected State; Varies by Context

The consequences vary depending on the type of resource and how it is used within the product.

Frequently Asked Questions

Want to get errata notifications? Sign up here.