linux-cve-announce - CVE-2023-53464: scsi: iscsi_tcp: Check that sock is valid before iscsi_set

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025100107-CVE-2023-53464-a397@gregkh>
Date: Wed,  1 Oct 2025 13:42:34 +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-53464: scsi: iscsi_tcp: Check that sock is valid before iscsi_set_param()

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

scsi: iscsi_tcp: Check that sock is valid before iscsi_set_param()

The validity of sock should be checked before assignment to avoid incorrect
values. Commit 57569c37f0ad ("scsi: iscsi: iscsi_tcp: Fix null-ptr-deref
while calling getpeername()") introduced this change which may lead to
inconsistent values of tcp_sw_conn->sendpage and conn->datadgst_en.

Fix the issue by moving the position of the assignment.

The Linux kernel CVE team has assigned CVE-2023-53464 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.10.150 with commit 884a788f065578bb640382279a83d1df433b13e6 and fixed in 5.10.178 with commit 499757ad3332e2527254f9ab68dec1da087b1d96
	Issue introduced in 5.15.75 with commit a26b0658751bb0a3b28386fca715333b104d32a2 and fixed in 5.15.107 with commit 5e5c5f472972c4bc9430adc08b36763a0fa5b9f7
	Issue introduced in 6.1 with commit 57569c37f0add1b6489e1a1563c71519daf732cf and fixed in 6.1.24 with commit 6e06a68fbbfcd8576eee8f7139fa2b13c9b72e91
	Issue introduced in 6.1 with commit 57569c37f0add1b6489e1a1563c71519daf732cf and fixed in 6.2.11 with commit b287e21e73ec23f3788fbe40037c42dbe6e9a9a9
	Issue introduced in 6.1 with commit 57569c37f0add1b6489e1a1563c71519daf732cf and fixed in 6.3 with commit 48b19b79cfa37b1e50da3b5a8af529f994c08901
	Issue introduced in 5.19.17 with commit 897dbbc57d71e8a34ec1af8e573a142de457da38
	Issue introduced in 6.0.3 with commit 0a0b861fce2657ba08ec356a74346b37ca4b2008

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-53464
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/scsi/iscsi_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/499757ad3332e2527254f9ab68dec1da087b1d96
	https://git.kernel.org/stable/c/5e5c5f472972c4bc9430adc08b36763a0fa5b9f7
	https://git.kernel.org/stable/c/6e06a68fbbfcd8576eee8f7139fa2b13c9b72e91
	https://git.kernel.org/stable/c/b287e21e73ec23f3788fbe40037c42dbe6e9a9a9
	https://git.kernel.org/stable/c/48b19b79cfa37b1e50da3b5a8af529f994c08901