{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2023-53643","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2025-10-07T15:16:59.658Z","datePublished":"2025-10-07T15:19:42.374Z","dateUpdated":"2026-08-05T09:15:19.014Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-08-05T09:15:19.014Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvme-tcp: don't access released socket during error recovery\n\nWhile the error recovery work is temporarily failing reconnect attempts,\nrunning the 'nvme list' command causes a kernel NULL pointer dereference\nby calling getsockname() with a released socket.\n\nDuring error recovery work, the nvme tcp socket is released and a new one\ncreated, so it is not safe to access the socket without proper check."}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:L - The dereference is reached only through a local sysfs read of `/sys/class/nvme/nvmeX/address`, which invokes `nvme_tcp_get_address()`; a remote peer can induce the vulnerable state by dropping the fabric connection but cannot itself complete the trigger.\nAC:L - The bad state persists for the full 10-second default reconnect_delay and recurs for up to 600 seconds of ctrl_loss_tmo, and the world-readable `state` attribute lets the attacker observe the `connecting` window and time the read deterministically — the commit itself reports a plain `nvme list` reproducing it.\nPR:L - The `address` attribute is `S_IRUGO` (0444), so any unprivileged local account can read it; no capability, namespace trick, or device access is needed.\nUI:N - The attacker performs the sysfs read directly and needs no victim action; the same crash also occurs unaided from routine monitoring tools such as `nvme list`.\nS:U - Impact is confined to the kernel of the host running the NVMe-TCP initiator, with no crossing of a VM, IOMMU, or other security-authority boundary.\nC:H - `nvme_tcp_free_queue()` releases the socket without clearing `queue->sock`, so `kernel_getsockname()` reads `ops` and address data from freed `sock_inode_cache` memory that an unprivileged user can reclaim by spraying sockets, and the result is copied into the world-readable sysfs buffer, disclosing kernel/other-socket state.\nI:H - The use-after-free performs an indirect call through `sock->ops->getname` loaded from freed, reclaimable slab memory, giving a control-flow hijack primitive once the attacker grooms the reclaimed object.\nA:H - In the common case `queue->sock` is NULL or points at a released socket with `ops` cleared, so the read produces an immediate kernel NULL pointer dereference and oops/panic, repeatable on demand."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/nvme/host/tcp.c"],"versions":[{"version":"02c57a82c0081141abc19150beab48ef47f97f18","lessThan":"fe2d9e54165dadaa0d0cc3355c0be9c3e129fa0d","status":"affected","versionType":"git"},{"version":"02c57a82c0081141abc19150beab48ef47f97f18","lessThan":"d82f762db4776fa11de88018f0f5de2d5db72a72","status":"affected","versionType":"git"},{"version":"02c57a82c0081141abc19150beab48ef47f97f18","lessThan":"76d54bf20cdcc1ed7569a89885e09636e9a8d71d","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/nvme/host/tcp.c"],"versions":[{"version":"6.1","status":"affected"},{"version":"0","lessThan":"6.1","status":"unaffected","versionType":"semver"},{"version":"6.1.18","lessThanOrEqual":"6.1.*","status":"unaffected","versionType":"semver"},{"version":"6.2.5","lessThanOrEqual":"6.2.*","status":"unaffected","versionType":"semver"},{"version":"6.3","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.1","versionEndExcluding":"6.1.18"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.1","versionEndExcluding":"6.2.5"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.1","versionEndExcluding":"6.3"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/fe2d9e54165dadaa0d0cc3355c0be9c3e129fa0d"},{"url":"https://git.kernel.org/stable/c/d82f762db4776fa11de88018f0f5de2d5db72a72"},{"url":"https://git.kernel.org/stable/c/76d54bf20cdcc1ed7569a89885e09636e9a8d71d"}],"title":"nvme-tcp: don't access released socket during error recovery","x_generator":{"engine":"bippy-1.2.0"}}}}