CVE-2026-89480

Description

A flaw was found in the NVMe-TCP implementation of the Linux kernel. This vulnerability occurs when the system completes a data read request even if the connected controller transfers fewer bytes than expected. As a result, the user application receives a mix of legitimate and stale data, potentially leading to information disclosure or data integrity issues.

Mitigation

Prevent the nvme-tcp kernel module from loading if NVMe-over-TCP storage connectivity is not required on the host:

1. Create a configuration file to blacklist the driver and prevent it from loading:
# echo "install nvme-tcp /bin/true" > /etc/modprobe.d/nvme-tcp.conf
# echo "blacklist nvme-tcp" >> /etc/modprobe.d/nvme-tcp.conf

2. If the module is currently loaded, unload it:
# modprobe -r nvme-tcp

Caveats:
Applying this operational workaround disables all NVMe-over-TCP initiator functionality and prevents connections to NVMe-oF network storage fabrics. If the module is actively in use by mounted file systems or active block devices, it cannot be safely unloaded at runtime without first unmounting those targets, and a system reboot may be required to cleanly unload the driver.

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).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score7N/A7.5
Attack VectorLocalN/ANetwork
Attack ComplexityHighN/ALow
Privileges RequiredLowN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityHighN/AHigh
Integrity ImpactHighN/ANone
Availability ImpactHighN/ANone

Vector

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

cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Understanding the Weakness (CWE)

Confidentiality,Integrity

Technical Impact: Read Memory; Modify Memory; Varies by Context

Frequently Asked Questions

Want to get errata notifications? Sign up here.