linux-kernel - Forwarded: Re: [syzbot] [rds?] general protection fault in rds_tcp_accept

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <698ad8a8.050a0220.1ad825.0060.GAE@google.com>
Date: Mon, 09 Feb 2026 23:05:12 -0800
From: syzbot <syzbot+96046021045ffe6d7709@...kaller.appspotmail.com>
To: linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: Forwarded: Re: [syzbot] [rds?] general protection fault in rds_tcp_accept_one

For archival purposes, forwarding an incoming command email to
linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com.

***

Subject: Re: [syzbot] [rds?] general protection fault in rds_tcp_accept_one
Author: allison.henderson@...cle.com

#syz test: git@...hub.com:allisonhenderson/rds_work.git rds_tcp_bug_fixes_v14

commit 86b003db7ed7f474c3f462643c2912ffdeb2f876
Author: Allison Henderson <achender@...nel.org>
Date:   Mon Feb 9 18:20:42 2026 -0700

    net/rds: Fix NULL pointer dereference in rds_tcp_accept_one
    
    Hold a local reference to new_sock->sk before installing callbacks
    in rds_tcp_accept_one. After rds_tcp_set_callbacks() or
    rds_tcp_reset_callbacks(), tc->t_sock is set to new_sock which
    may race with the shutdown path.  A concurrent
    rds_tcp_conn_path_shutdown() may call sock_release(), which sets
    new_sock->sk = NULL and frees sk.
    
    Subsequent accesses to new_sock->sk->sk_state dereference NULL,
    causing the null dereference. So a local sock reference with
    sock_hold() before installing callbacks will prevent the race.
    
    Fixes: 826c1004d4ae ("net/rds: rds_tcp_conn_path_shutdown must not discard messages")
    Reported-by: syzbot+96046021045ffe6d7709@...kaller.appspotmail.com
    Closes: https://syzkaller.appspot.com/bug?extid=96046021045ffe6d7709
    Signed-off-by: Allison Henderson <achender@...nel.org>

diff --git a/net/rds/tcp_listen.c b/net/rds/tcp_listen.c
index 6fb5c928b8fd..cdc86473a1ba 100644
--- a/net/rds/tcp_listen.c
+++ b/net/rds/tcp_listen.c
@@ -177,6 +177,7 @@ int rds_tcp_accept_one(struct rds_tcp_net *rtn)
 	struct rds_tcp_connection *rs_tcp = NULL;
 	int conn_state;
 	struct rds_conn_path *cp;
+	struct sock *sk;
 	struct in6_addr *my_addr, *peer_addr;
 #if !IS_ENABLED(CONFIG_IPV6)
 	struct in6_addr saddr, daddr;
@@ -298,6 +299,14 @@ int rds_tcp_accept_one(struct rds_tcp_net *rtn)
 		rds_conn_path_drop(cp, 0);
 		goto rst_nsk;
 	}
+	/* Hold a local reference to sk before setting callbacks. Once callbacks
+	 * are set, it is possible for a concurrent rds_tcp_conn_path_shutdown
+	 * call to release the new_sock->sk and set it to NULL.  So we use
+	 * a local sk here to avoid racing with callbacks
+	 */
+	sk = new_sock->sk;
+	sock_hold(sk);
+
 	if (rs_tcp->t_sock) {
 		/* Duelling SYN has been handled in rds_tcp_accept_one() */
 		rds_tcp_reset_callbacks(new_sock, cp);
@@ -316,13 +325,15 @@ int rds_tcp_accept_one(struct rds_tcp_net *rtn)
 	 * knowing that "rds_tcp_conn_path_shutdown" will
 	 * dequeue pending messages.
 	 */
-	if (new_sock->sk->sk_state == TCP_CLOSE_WAIT ||
-	    new_sock->sk->sk_state == TCP_LAST_ACK ||
-	    new_sock->sk->sk_state == TCP_CLOSE)
+	if (READ_ONCE(sk->sk_state) == TCP_CLOSE_WAIT ||
+	    READ_ONCE(sk->sk_state) == TCP_LAST_ACK ||
+	    READ_ONCE(sk->sk_state) == TCP_CLOSE)
 		rds_conn_path_drop(cp, 0);
 	else
 		queue_delayed_work(cp->cp_wq, &cp->cp_recv_w, 0);
 
+	sock_put(sk);
+
 	new_sock = NULL;
 	ret = 0;
 	if (conn->c_npaths == 0)