* [PATCH net v1] net/smc: fix socket use-after-free during link group termination
@ 2026-07-23 10:54 xuanqiang.luo
2026-07-24 10:56 ` sashiko-bot
2026-07-28 9:32 ` patchwork-bot+netdevbpf
0 siblings, 2 replies; 3+ messages in thread
From: xuanqiang.luo @ 2026-07-23 10:54 UTC (permalink / raw)
To: netdev
Cc: alibuda, dust.li, sidraya, wenjia, mjambigi, tonylu, guwen, davem,
edumazet, kuba, pabeni, horms, kgraul, ubraun, linux-rdma,
linux-s390, Xuanqiang Luo, stable
From: Xuanqiang Luo <luoxuanqiang@kylinos.cn>
__smc_lgr_terminate() drops conns_lock after finding a connection in
lgr->conns_all, but before taking a reference on its socket. The connection
is embedded in the socket, and its registration reference protects it only
while the connection remains in the tree.
A concurrent close can unregister the connection and drop that reference,
freeing the socket before the termination worker reaches sock_hold().
The race is reachable when close overlaps link group termination.
Local stress testing reproduced the use-after-free and KASAN reported:
BUG: KASAN: slab-use-after-free in __smc_lgr_terminate.part.0 [smc]
Write of size 4 by task kworker/3:3
Workqueue: events smc_lgr_terminate_work [smc]
__smc_lgr_terminate.part.0 [smc]
The socket was allocated by smc_create(), freed through
slab_free_after_rcu_debug(), and was followed by:
refcount_t: addition on 0; use-after-free.
__smc_lgr_terminate.part.0 [smc]
Take the socket reference while conns_lock still protects the tree entry.
The unregister path then cannot drop the last reference until termination
has finished using the socket.
Fixes: 69318b5215f2 ("net/smc: improve abnormal termination locking")
Cc: stable@vger.kernel.org
Signed-off-by: Xuanqiang Luo <luoxuanqiang@kylinos.cn>
---
net/smc/smc_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/smc/smc_core.c b/net/smc/smc_core.c
index cf6b620fef05f..b4208cb186c5e 100644
--- a/net/smc/smc_core.c
+++ b/net/smc/smc_core.c
@@ -1572,10 +1572,10 @@ static void __smc_lgr_terminate(struct smc_link_group *lgr, bool soft)
read_lock_bh(&lgr->conns_lock);
node = rb_first(&lgr->conns_all);
while (node) {
- read_unlock_bh(&lgr->conns_lock);
conn = rb_entry(node, struct smc_connection, alert_node);
smc = container_of(conn, struct smc_sock, conn);
sock_hold(&smc->sk); /* sock_put below */
+ read_unlock_bh(&lgr->conns_lock);
lock_sock(&smc->sk);
smc_conn_kill(conn, soft);
release_sock(&smc->sk);
--
2.43.0
^ permalink raw reply related [flat|nested] 3+ messages in thread* Re: [PATCH net v1] net/smc: fix socket use-after-free during link group termination
2026-07-23 10:54 [PATCH net v1] net/smc: fix socket use-after-free during link group termination xuanqiang.luo
@ 2026-07-24 10:56 ` sashiko-bot
2026-07-28 9:32 ` patchwork-bot+netdevbpf
1 sibling, 0 replies; 3+ messages in thread
From: sashiko-bot @ 2026-07-24 10:56 UTC (permalink / raw)
To: xuanqiang.luo
Cc: Heiko Carstens, linux-s390, Vasily Gorbik, Alexander Gordeev
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
Pre-existing issues:
- [High] Socket reference count leak in smc_switch_conns() error path.
- [High] Concurrent execution of smc_close_active_abort() and smc_clcsock_release() can lead to a TOCTOU NULL pointer dereference or Use-After-Free.
--
--- Patch [1]: [PATCH net v1] net/smc: fix socket use-after-free during link group termination ---
commit d8af9113083c00ced5108b5d3f34199756d886c8
Author: Xuanqiang Luo <luoxuanqiang@kylinos.cn>
net/smc: fix socket use-after-free during link group termination
This patch fixes a socket use-after-free in __smc_lgr_terminate() by
taking a reference on the socket while the link group connection lock
is still held.
> diff --git a/net/smc/smc_core.c b/net/smc/smc_core.c
> index cf6b620fef05f..b4208cb186c5e 100644
> --- a/net/smc/smc_core.c
> +++ b/net/smc/smc_core.c
> @@ -1572,10 +1572,10 @@ static void __smc_lgr_terminate(struct smc_link_group *lgr, bool soft)
> read_lock_bh(&lgr->conns_lock);
> node = rb_first(&lgr->conns_all);
> while (node) {
> - read_unlock_bh(&lgr->conns_lock);
> conn = rb_entry(node, struct smc_connection, alert_node);
> smc = container_of(conn, struct smc_sock, conn);
> sock_hold(&smc->sk); /* sock_put below */
> + read_unlock_bh(&lgr->conns_lock);
> lock_sock(&smc->sk);
> smc_conn_kill(conn, soft);
[Severity: High]
This is a pre-existing issue, but I noticed a potential race condition
involving smc_close_active_abort() when called via smc_conn_kill() from here.
Does this code risk a use-after-free if smc_clcsock_release() is running
concurrently?
When another thread runs __smc_release(), it explicitly drops the socket lock
before calling smc_clcsock_release():
net/smc/af_smc.c:__smc_release() {
release_sock(sk);
smc_clcsock_release(smc);
lock_sock(sk);
}
This allows smc_close_active_abort() to run concurrently and dereference
smc->clcsock without holding the clcsock_release_lock:
net/smc/smc_close.c:smc_close_active_abort() {
if (sk->sk_state != SMC_INIT && smc->clcsock && smc->clcsock->sk) {
sk->sk_err = ECONNABORTED;
if (smc->clcsock && smc->clcsock->sk)
tcp_abort(smc->clcsock->sk, ECONNABORTED);
}
}
If smc_clcsock_release() zeroes and frees the underlying TCP socket at the
exact same time, could passing smc->clcsock->sk to tcp_abort() crash?
> release_sock(&smc->sk);
[ ... ]
While reviewing the above, I also noticed another pre-existing issue in the
same file.
[Severity: High]
This isn't a bug introduced by this patch, but does the error path in
smc_switch_conns() leak a socket reference?
The loop acquires a socket reference to protect it across the sleepable
buffer fetch:
net/smc/smc_core.c:smc_switch_conns() {
sock_hold(&smc->sk);
...
if (rc)
goto err_out;
}
However, the err_out label completely lacks the corresponding sock_put()
cleanup to balance the reference:
net/smc/smc_core.c:smc_switch_conns() {
err_out:
smcr_link_down_cond_sched(to_lnk);
smc_wr_tx_link_put(to_lnk);
return NULL;
}
Could this cause memory exhaustion over time if a connection switch fails?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260723105454.87016-1-xuanqiang.luo@linux.dev?part=1
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [PATCH net v1] net/smc: fix socket use-after-free during link group termination
2026-07-23 10:54 [PATCH net v1] net/smc: fix socket use-after-free during link group termination xuanqiang.luo
2026-07-24 10:56 ` sashiko-bot
@ 2026-07-28 9:32 ` patchwork-bot+netdevbpf
1 sibling, 0 replies; 3+ messages in thread
From: patchwork-bot+netdevbpf @ 2026-07-28 9:32 UTC (permalink / raw)
To: luoxuanqiang
Cc: netdev, alibuda, dust.li, sidraya, wenjia, mjambigi, tonylu,
guwen, davem, edumazet, kuba, pabeni, horms, kgraul, ubraun,
linux-rdma, linux-s390, luoxuanqiang, stable
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 23 Jul 2026 18:54:54 +0800 you wrote:
> From: Xuanqiang Luo <luoxuanqiang@kylinos.cn>
>
> __smc_lgr_terminate() drops conns_lock after finding a connection in
> lgr->conns_all, but before taking a reference on its socket. The connection
> is embedded in the socket, and its registration reference protects it only
> while the connection remains in the tree.
>
> [...]
Here is the summary with links:
- [net,v1] net/smc: fix socket use-after-free during link group termination
https://git.kernel.org/netdev/net/c/f621d6ebeebb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2026-07-28 9:33 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-07-23 10:54 [PATCH net v1] net/smc: fix socket use-after-free during link group termination xuanqiang.luo
2026-07-24 10:56 ` sashiko-bot
2026-07-28 9:32 ` patchwork-bot+netdevbpf
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox