CVE-2026-89968
Description
A flaw was found in the nvmet-tcp component of the Linux kernel. A remote attacker can exploit this vulnerability by sending an unsolicited H2CData PDU (Protocol Data Unit) before the target transmits an R2T (Ready To Transfer) for a write command. This can cause the command to be completed twice, leading to a kernel bug or a soft-lockup. The most significant consequence is a Denial of Service (DoS) condition, making the system unresponsive.
Statement
An unsolicited H2CData PDU in the NVMe/TCP target path can be accepted before the target has sent an R2T for the command. A remote host can submit a write command that takes the R2T path and then send H2CData for the same tag before R2T is transmitted, causing early command completion and a later second completion on an error path. This can add the same command to the response list twice and create a self referential list node, resulting in a kernel BUG with CONFIG_DEBUG_LIST or a wedged nvmet_tcp workqueue and soft lockup without it. For the CVSS the PR:N is used for the paranoid score because an allow_any_host subsystem can be reached without authentication once the attacker has access to the NVMe/TCP target network. The issue is network reachable inside the storage fabric, but NVMe/TCP targets are usually deployed on isolated storage or data center networks rather than the public Internet. Impact is at least denial of service via kernel crash or workqueue lockup and in worst case may allow limited confidentiality or integrity impact due to kernel list state corruption and should be reviewed manually.
Mitigation
Mitigation for this issue is either not available or the currently available options don't 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 Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.5 | N/A | 7.5 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | None | N/A | None |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory)
An attacker could provide unexpected values and cause a program crash or arbitrary control of resource allocation, leading to excessive consumption of resources such as memory and CPU.
Confidentiality
Technical Impact: Read Memory; Read Files or Directories
An attacker could read confidential data if they are able to control resource references.
Integrity,Confidentiality,Availability
Technical Impact: Modify Memory; Execute Unauthorized Code or Commands
An attacker could use malicious input to modify data or possibly alter control flow in unexpected ways, including arbitrary command execution.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.