[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025100716-CVE-2023-53643-4725@gregkh>
Date: Tue, 7 Oct 2025 17:19:48 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53643: nvme-tcp: don't access released socket during error recovery
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
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.
The Linux kernel CVE team has assigned CVE-2023-53643 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.1 with commit 02c57a82c0081141abc19150beab48ef47f97f18 and fixed in 6.1.18 with commit fe2d9e54165dadaa0d0cc3355c0be9c3e129fa0d
Issue introduced in 6.1 with commit 02c57a82c0081141abc19150beab48ef47f97f18 and fixed in 6.2.5 with commit d82f762db4776fa11de88018f0f5de2d5db72a72
Issue introduced in 6.1 with commit 02c57a82c0081141abc19150beab48ef47f97f18 and fixed in 6.3 with commit 76d54bf20cdcc1ed7569a89885e09636e9a8d71d
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2023-53643
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/nvme/host/tcp.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/fe2d9e54165dadaa0d0cc3355c0be9c3e129fa0d
https://git.kernel.org/stable/c/d82f762db4776fa11de88018f0f5de2d5db72a72
https://git.kernel.org/stable/c/76d54bf20cdcc1ed7569a89885e09636e9a8d71d
Powered by blists - more mailing lists