LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53643: nvme-tcp: don't access released socket during error recovery

In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: don't access released socket during error recovery While the error recovery work is temporarily failing reconnect attempts, running the 'nvme list' command causes a kernel NULL pointer dereference by calling getsockname() with a released socket. During error recovery work, the nvme tcp socket is released and a new one created, so it is not safe to access the socket without proper check.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash affected systems using NVMe over TCP during storage error recovery. The public record describes a NULL pointer dereference triggered when a socket has already been released. Business impact is most relevant for systems that depend on NVMe/TCP storage availability.

Executive priority

Treat as a targeted availability risk for Linux storage infrastructure, not a broad internet emergency. Prioritize patch validation for production NVMe/TCP hosts because kernel crashes can disrupt dependent services.

Technical view

The nvme-tcp code could call getsockname() on a released socket while reconnect attempts were temporarily failing during error recovery. The source says running nvme list in that state causes a kernel NULL pointer dereference. Linux stable commits are referenced as the resolution.

Likely exposure

Exposure appears limited to Linux systems using NVMe/TCP on affected kernel versions. The affected-version data in the bundle is sparse and should be validated against distribution kernel advisories and backport status.

Exploitation context

The bundle does not show CISA KEV listing, public exploitation, CVSS, CWE, or an attacker-controlled path. The documented trigger involves NVMe/TCP error recovery and nvme list during reconnect failure.

Researcher notes

Evidence supports a reliability flaw in nvme-tcp socket lifetime handling. Public source data does not establish exploitability beyond the documented crash condition, and affected-version metadata appears incomplete or ambiguous.

Mitigation direction

  • Apply a vendor kernel update containing the referenced Linux stable fixes.
  • Check distribution advisories for backported fixes and exact fixed package versions.
  • Prioritize systems where NVMe/TCP supports production storage paths.
  • Avoid inventing workarounds; follow Linux or distribution vendor guidance.

Validation and detection

  • Inventory Linux hosts using NVMe/TCP storage.
  • Compare running kernels against vendor fixed versions or referenced stable commits.
  • Review kernel logs for NULL pointer dereference events involving nvme-tcp recovery.
  • Confirm storage monitoring covers reconnect failures and unexpected host crashes.
Prepared
Confidence
medium
Sources
5

Public sources used

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-2023-53643 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux02c57a82c0081141abc19150beab48ef47f97f18, 02c57a82c0081141abc19150beab48ef47f97f18, 02c57a82c0081141abc19150beab48ef47f97f18unaffected
LinuxLinux6.1, 0, 6.1.18, 6.2.5, 6.3affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.