CVE-2025-38264
Description
From CVE.org
In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: sanitize request list handling Validate the request in nvme_tcp_handle_r2t() to ensure it's not part of any list, otherwise a malicious R2T PDU might inject a loop in request list processing.
Statement
The vulnerability lies in the lack of validation for list membership in nvme_tcp_handle_r2t(), potentially allowing malicious R2T PDUs to introduce list corruption or loops. This could lead to denial of service or memory corruption. The Privileges for the CVSS is Low as the attacker only needs access to an NVMe TCP queue, which may be exposed via user-level networking or containerized environments. This bug can be triggered remotely if a Linux system connects to a malicious or compromised NVMe-over-TCP target. The attacker, by crafting a malformed R2T PDU, could cause list corruption in the initiator’s kernel, potentially leading to memory corruption or denial of service. The issue is not locally triggerable by userspace but can be remotely exploited by an attacker controlling the target. The config option CONFIG_NVME_COMMON disabled in all versions of Red Hat Enterprise Linux, so as result all versions are not affected.
Mitigation
Check if Kernel config option CONFIG_NVME_COMMON disabled or could be disabled. If disabled, then not vulnerable.
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 Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.1 | 5.5 | 9.8 |
| Attack Vector | Adjacent Network | Local | Network |
| Attack Complexity | High | Low | Low |
| Privileges Required | Low | Low | None |
| User Interaction | None | None | None |
| Scope | Unchanged | Unchanged | Unchanged |
| Confidentiality | High | None | High |
| Integrity Impact | High | None | High |
| Availability Impact | High | High | High |
Vector
Red Hat: CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD: 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:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Integrity,Confidentiality
Technical Impact: Modify Application Data; Read Application Data
If a released resource is subsequently reused or reallocated, then an attempt to use the original resource might allow access to sensitive data that is associated with a different user or entity.
Other,Availability
Technical Impact: Other; DoS: Crash, Exit, or Restart
When a resource is released it might not be in an expected state, later attempts to access the resource may lead to resultant errors that may lead to a crash.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
