Netdev List
 help / color / mirror / Atom feed
From: Mahanta Jambigi <mjambigi@linux.ibm.com>
To: xuanqiang.luo@linux.dev, netdev@vger.kernel.org
Cc: alibuda@linux.alibaba.com, dust.li@linux.alibaba.com,
	sidraya@linux.ibm.com, wenjia@linux.ibm.com,
	tonylu@linux.alibaba.com, guwen@linux.alibaba.com,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, kgraul@linux.ibm.com,
	ubraun@linux.ibm.com, linux-rdma@vger.kernel.org,
	linux-s390@vger.kernel.org,
	Xuanqiang Luo <luoxuanqiang@kylinos.cn>,
	stable@vger.kernel.org
Subject: Re: [PATCH net v1] net/smc: fix socket use-after-free during link group termination
Date: Thu, 23 Jul 2026 18:42:16 +0530	[thread overview]
Message-ID: <afe502a5-7c42-4dbe-812b-9b072c819d25@linux.ibm.com> (raw)
In-Reply-To: <20260723105454.87016-1-xuanqiang.luo@linux.dev>



On 23/07/26 4:24 pm, xuanqiang.luo@linux.dev 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.
> 
> 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.

The race description and fix look correct to me. Taking the socket
reference before dropping *conns_lock* closes the window where a
concurrent close can free the socket before sock_hold().

> 
> Fixes: 69318b5215f2 ("net/smc: improve abnormal termination locking")
> Cc: stable@vger.kernel.org
> Signed-off-by: Xuanqiang Luo <luoxuanqiang@kylinos.cn>

Reviewed-by: Mahanta Jambigi <mjambigi@linux.ibm.com>

> ---
>  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);


  reply	other threads:[~2026-07-23 13:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23 10:54 [PATCH net v1] net/smc: fix socket use-after-free during link group termination xuanqiang.luo
2026-07-23 13:12 ` Mahanta Jambigi [this message]
2026-07-28  9:32 ` patchwork-bot+netdevbpf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=afe502a5-7c42-4dbe-812b-9b072c819d25@linux.ibm.com \
    --to=mjambigi@linux.ibm.com \
    --cc=alibuda@linux.alibaba.com \
    --cc=davem@davemloft.net \
    --cc=dust.li@linux.alibaba.com \
    --cc=edumazet@google.com \
    --cc=guwen@linux.alibaba.com \
    --cc=horms@kernel.org \
    --cc=kgraul@linux.ibm.com \
    --cc=kuba@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=luoxuanqiang@kylinos.cn \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sidraya@linux.ibm.com \
    --cc=stable@vger.kernel.org \
    --cc=tonylu@linux.alibaba.com \
    --cc=ubraun@linux.ibm.com \
    --cc=wenjia@linux.ibm.com \
    --cc=xuanqiang.luo@linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox