From: Leon Romanovsky <leon@kernel.org>
To: Wentao Liang <vulab@iscas.ac.cn>
Cc: bernard.metzler@linux.dev, jgg@ziepe.ca,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 6/7] RDMA/siw: Fix new_cep use-after-free in siw_accept_newconn()
Date: Wed, 23 Sep 2026 11:08:01 +0300 [thread overview]
Message-ID: <20260923080801.GL563127@unreal> (raw)
In-Reply-To: <20260916184109.2092928-1-vulab@iscas.ac.cn>
On Wed, Sep 16, 2026 at 06:41:09PM +0000, Wentao Liang wrote:
> On the error path the listening endpoint reference of new_cep is
> dropped before the accepted socket is disassociated. When only the
> socket's reference remains, siw_socket_disassoc() drops that last
> reference and frees the endpoint, leaving the subsequent
> 'new_cep->sock = NULL' writing into freed memory.
>
> Tear the accepted socket down first and put the endpoint last.
>
> Fixes: 6c52fdc244b5 ("rdma/siw: connection management")
> Cc: stable@vger.kernel.org
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
> ---
> drivers/infiniband/sw/siw/siw_cm.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
I think this patch is supposed to fix it:
https://patch.msgid.link/r/20260604160808.30948-1-bernard.metzler@linux.dev
Thanks
>
> diff --git a/drivers/infiniband/sw/siw/siw_cm.c b/drivers/infiniband/sw/siw/siw_cm.c
> index f7ac81c0f267..1b93963cb191 100644
> --- a/drivers/infiniband/sw/siw/siw_cm.c
> +++ b/drivers/infiniband/sw/siw/siw_cm.c
> @@ -1044,14 +1044,16 @@ static void siw_accept_newconn(struct siw_cep *cep)
> return;
>
> error:
> - if (new_cep)
> - siw_cep_put(new_cep);
> -
> if (new_s) {
> siw_socket_disassoc(new_s);
> sock_release(new_s);
> - new_cep->sock = NULL;
> + if (new_cep)
> + new_cep->sock = NULL;
> }
> +
> + if (new_cep)
> + siw_cep_put(new_cep);
> +
> siw_dbg_cep(cep, "error %d\n", rv);
> }
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2026-09-23 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 18:41 Wentao Liang
2026-09-23 8:08 ` Leon Romanovsky [this message]
2026-09-28 12:16 ` Bernard Metzler
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=20260923080801.GL563127@unreal \
--to=leon@kernel.org \
--cc=bernard.metzler@linux.dev \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=vulab@iscas.ac.cn \
/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
all inboxes | Powered by JetHome®