Security readout for executives and security teams
Plain-English summary
CVE-2025-38035 is a Linux kernel denial-of-service flaw in the NVMe-over-TCP target path. Under a connection timing condition, the kernel may install a null socket callback; later TCP processing can call it and crash the host. The business impact is loss of availability on affected storage targets. The supplied CVSS score is 7.5; confidentiality and integrity impacts are not claimed.
Executive priority
High for organizations operating reachable or business-critical NVMe-over-TCP targets. Patch promptly after compatibility testing, using emergency handling for exposed or availability-sensitive storage infrastructure. Priority is lower for systems confirmed not to provide this service. Current evidence supports host crashes and service disruption, not theft or modification of data.
Technical view
If nvmet_tcp_set_queue_sock() runs before the TCP connection is established, queue->state_change can remain NULL because the socket callback was not replaced. Cleanup incorrectly restores that NULL value. Later TCP state processing, including FIN handling, may invoke the null callback, causing a kernel NULL-pointer dereference and system crash. Referenced Linux stable commits prevent restoration when no saved callback exists.
Likely exposure
Likely exposure is limited to Linux systems operating the NVMe-over-TCP target component, particularly where untrusted initiators can reach its TCP service. The record identifies affected kernel lines from 5.0 through 6.15, but its flattened version data does not establish dependable package boundaries. Systems not providing NVMe-over-TCP target service are unlikely to exercise this path.
Exploitation context
The supplied vector is network-accessible, low-complexity, unauthenticated, and requires no user interaction. However, the bundle provides no exploit procedure. KEV is false, and no cited source reports active exploitation. Treat this as potentially remotely triggerable denial of service, not demonstrated code execution or data compromise.
Researcher notes
Crash evidence shows instruction execution at address zero during TCP receive and FIN processing. The correction guards callback restoration when queue->state_change is NULL. The supplied description is truncated, and its version representation is ambiguous; researchers should verify exact vulnerable and corrected boundaries against the relevant stable branch or distribution package advisory.
Mitigation direction
Update affected NVMe-over-TCP targets to a vendor kernel containing the referenced stable fix.
Prioritize broadly reachable NVMe-over-TCP services and high-availability storage infrastructure.
If patching is delayed, restrict NVMe-over-TCP access to trusted initiators using existing network controls.
Check distribution advisories for exact packages; the bundle does not provide reliable package boundaries.
Validation and detection
Inventory Linux hosts acting as NVMe-over-TCP targets and determine whether nvmet-tcp is actively used.
Record running kernel packages and map them to distribution advisories or the referenced stable commits.
Confirm the corrected kernel is active after the maintenance reboot.
Review kernel logs for NULL dereferences, RIP address zero, nvmet-tcp, or tcp_fin-related crashes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-38035 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
11Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.