linux-cve-announce - CVE-2023-53110: net/smc: fix NULL sndbuf_desc in smc_cdc_tx

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: <2025050227-CVE-2023-53110-2b28@gregkh>
Date: Fri,  2 May 2025 17:56:15 +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-53110: net/smc: fix NULL sndbuf_desc in smc_cdc_tx_handler()

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

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

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

net/smc: fix NULL sndbuf_desc in smc_cdc_tx_handler()

When performing a stress test on SMC-R by rmmod mlx5_ib driver
during the wrk/nginx test, we found that there is a probability
of triggering a panic while terminating all link groups.

This issue dues to the race between smc_smcr_terminate_all()
and smc_buf_create().

			smc_smcr_terminate_all

smc_buf_create
/* init */
conn->sndbuf_desc = NULL;
...

			__smc_lgr_terminate
				smc_conn_kill
					smc_close_abort
						smc_cdc_get_slot_and_msg_send

			__softirqentry_text_start
				smc_wr_tx_process_cqe
					smc_cdc_tx_handler
						READ(conn->sndbuf_desc->len);
						/* panic dues to NULL sndbuf_desc */

conn->sndbuf_desc = xxx;

This patch tries to fix the issue by always to check the sndbuf_desc
before send any cdc msg, to make sure that no null pointer is
seen during cqe processing.

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


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

	Issue introduced in 5.5 with commit 0b29ec6436138721acf5844e558f7334a0fa61d5 and fixed in 5.10.176 with commit 31817c530768b0199771ec6019571b4f0ddbf230
	Issue introduced in 5.5 with commit 0b29ec6436138721acf5844e558f7334a0fa61d5 and fixed in 5.15.104 with commit b108bd9e6be000492ebebe867daa699285978a10
	Issue introduced in 5.5 with commit 0b29ec6436138721acf5844e558f7334a0fa61d5 and fixed in 6.1.21 with commit 3c270435db8aa34929263dddae8fd050f5216ecb
	Issue introduced in 5.5 with commit 0b29ec6436138721acf5844e558f7334a0fa61d5 and fixed in 6.2.8 with commit 3ebac7cf0a184a8102821a7a00203f02bebda83c
	Issue introduced in 5.5 with commit 0b29ec6436138721acf5844e558f7334a0fa61d5 and fixed in 6.3 with commit 22a825c541d775c1dbe7b2402786025acad6727b

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-53110
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:
	net/smc/smc_cdc.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/31817c530768b0199771ec6019571b4f0ddbf230
	https://git.kernel.org/stable/c/b108bd9e6be000492ebebe867daa699285978a10
	https://git.kernel.org/stable/c/3c270435db8aa34929263dddae8fd050f5216ecb
	https://git.kernel.org/stable/c/3ebac7cf0a184a8102821a7a00203f02bebda83c
	https://git.kernel.org/stable/c/22a825c541d775c1dbe7b2402786025acad6727b