Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Wentao Liang <vulab@iscas.ac.cn>
To: bernard.metzler@linux.dev
Cc: jgg@ziepe.ca, leon@kernel.org, linux-kernel@vger.kernel.org,
	linux-rdma@vger.kernel.org, Wentao Liang <vulab@iscas.ac.cn>,
	stable@vger.kernel.org
Subject: [PATCH 6/7] RDMA/siw: Fix new_cep use-after-free in siw_accept_newconn()
Date: Wed, 16 Sep 2026 18:41:09 +0000	[thread overview]
Message-ID: <20260916184109.2092928-1-vulab@iscas.ac.cn> (raw)

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

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


             reply	other threads:[~2026-09-16 18:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 18:41 Wentao Liang [this message]
2026-09-23  8:08 ` [PATCH 6/7] RDMA/siw: Fix new_cep use-after-free in siw_accept_newconn() Leon Romanovsky
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=20260916184109.2092928-1-vulab@iscas.ac.cn \
    --to=vulab@iscas.ac.cn \
    --cc=bernard.metzler@linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /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