linux-cve-announce - CVE-2023-54318: net/smc: use smc_lgr_list.lock to protect smc_lgr_list.list iterate in smcr_port

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: <2025123038-CVE-2023-54318-bb2a@gregkh>
Date: Tue, 30 Dec 2025 13:24:11 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-54318: net/smc: use smc_lgr_list.lock to protect smc_lgr_list.list iterate in smcr_port_add

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

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

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

net/smc: use smc_lgr_list.lock to protect smc_lgr_list.list iterate in smcr_port_add

While doing smcr_port_add, there maybe linkgroup add into or delete
from smc_lgr_list.list at the same time, which may result kernel crash.
So, use smc_lgr_list.lock to protect smc_lgr_list.list iterate in
smcr_port_add.

The crash calltrace show below:
BUG: kernel NULL pointer dereference, address: 0000000000000000
PGD 0 P4D 0
Oops: 0000 [#1] SMP NOPTI
CPU: 0 PID: 559726 Comm: kworker/0:92 Kdump: loaded Tainted: G
Hardware name: Alibaba Cloud Alibaba Cloud ECS, BIOS 449e491 04/01/2014
Workqueue: events smc_ib_port_event_work [smc]
RIP: 0010:smcr_port_add+0xa6/0xf0 [smc]
RSP: 0000:ffffa5a2c8f67de0 EFLAGS: 00010297
RAX: 0000000000000001 RBX: ffff9935e0650000 RCX: 0000000000000000
RDX: 0000000000000010 RSI: ffff9935e0654290 RDI: ffff9935c8560000
RBP: 0000000000000000 R08: 0000000000000000 R09: ffff9934c0401918
R10: 0000000000000000 R11: ffffffffb4a5c278 R12: ffff99364029aae4
R13: ffff99364029aa00 R14: 00000000ffffffed R15: ffff99364029ab08
FS:  0000000000000000(0000) GS:ffff994380600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000f06a10003 CR4: 0000000002770ef0
PKRU: 55555554
Call Trace:
 smc_ib_port_event_work+0x18f/0x380 [smc]
 process_one_work+0x19b/0x340
 worker_thread+0x30/0x370
 ? process_one_work+0x340/0x340
 kthread+0x114/0x130
 ? __kthread_cancel_work+0x50/0x50
 ret_from_fork+0x1f/0x30

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


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

	Issue introduced in 5.8 with commit 1f90a05d9ff907c70456e7c9d7058372679a88c6 and fixed in 5.10.195 with commit d1c6c93c27a4bf48006ab16cd9b38d85559d7645
	Issue introduced in 5.8 with commit 1f90a05d9ff907c70456e7c9d7058372679a88c6 and fixed in 5.15.132 with commit 06b4934ab2b534bb92935c7601852066ebb9eab8
	Issue introduced in 5.8 with commit 1f90a05d9ff907c70456e7c9d7058372679a88c6 and fixed in 6.1.54 with commit 70c8d17007dc4a07156b7da44509527990e569b3
	Issue introduced in 5.8 with commit 1f90a05d9ff907c70456e7c9d7058372679a88c6 and fixed in 6.5.4 with commit b717463610a27fc0b58484cfead7a623d5913e61
	Issue introduced in 5.8 with commit 1f90a05d9ff907c70456e7c9d7058372679a88c6 and fixed in 6.6 with commit f5146e3ef0a9eea405874b36178c19a4863b8989

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-54318
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_core.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/d1c6c93c27a4bf48006ab16cd9b38d85559d7645
	https://git.kernel.org/stable/c/06b4934ab2b534bb92935c7601852066ebb9eab8
	https://git.kernel.org/stable/c/70c8d17007dc4a07156b7da44509527990e569b3
	https://git.kernel.org/stable/c/b717463610a27fc0b58484cfead7a623d5913e61
	https://git.kernel.org/stable/c/f5146e3ef0a9eea405874b36178c19a4863b8989