From nobody Thu Apr 2 23:53:32 2026 Received: from mail-ot1-f70.google.com (mail-ot1-f70.google.com [209.85.210.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 99E613EBF2C for ; Sun, 15 Feb 2026 06:09:07 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.210.70 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771135748; cv=none; b=pklMDAgaJVMg+wyKza64tK23QTp2+JsrT/eCeSX2+Fnb6IHMLFc5h/6VUFpaDWY71aP1SNch3JwYnMjQAbWA1K6HvKxnXzJ0vEhDprcx3SEDd2d/7KwLg7NkMXMPBu+o0cOUB8tt9IcB2i6rM5ISH8yB1ZRmp2Yeh73X7Vmbp7U= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771135748; c=relaxed/simple; bh=z0qumjUudldpor4P1SETtP3qDy1dXzy3jl/RIX+g3aI=; h=MIME-Version:Date:In-Reply-To:Message-ID:Subject:From:To: Content-Type; b=Y54dKpy6Z0TMPcnqfLpO1WYaBoH3qMRF/2JY83cUAEHOQXIWft5rBPVDvCZdqrS246lj9PB0otNco0LaN9uhapRoriMhQymvdBAJUPoh+1q4L8vinSE+sjMcY2P2B3o+1QVhgcjCQhhBtvVDiObzW5huMmsSKVtwWawao5WPX1w= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.210.70 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-ot1-f70.google.com with SMTP id 46e09a7af769-7d49709f87aso18631502a34.1 for ; Sat, 14 Feb 2026 22:09:07 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1771135746; x=1771740546; h=to:from:subject:message-id:in-reply-to:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=QKbkbebXbDa+X1D81bUtxMgXRRzPo6w++Y6f6Jhj1ks=; b=rPdw/RR8XpO5x5iaWeAzTEAfeKx4ZC9soAwD0YSmMBFRjGaEQdppaTE9FFA4XQgY9B y1bkgB13fjlxNXDIq+4JTqEaLlliYoELY1mwzjpoZUUq2FG45LACrm15rHY2vdurH9aI a4zE5C9eM7lr35Q36HUYyWgnNMLoDQEbI6pXimjzdvEXrTLJ1wkCNhk/uDJ5wq7x7YjF YrV5M1hw8bK3d7ASCtoqJlg8eF3R8wL6+YRkTPfTMdJYQNoEp7tZYhkynXQXYPHHZflJ at2s2O7vUsadc32W5gQ0UMhuhqOqmDVkUq8bEbPRf1KE92JhT11TGkqzwNwT10o2o/Wx qszA== X-Gm-Message-State: AOJu0Yyke3/hlv1r9k+a62ybMqKKjLb8FuiwkFqsL1eJj/AQQCrvGSRj CKO1M4S99lM8VZdFLiRSYhW6GPWCDmMtdxnjOxBLIFz1xrnM08lHvXM/W0h+BwLOQkTYjLu+5u8 XbHH/QkwyqoWPGHB6v1rFlGvvsR/pRg0gH9rTaORdsD4ZhLzKrE4FzUIchg4= Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6820:2297:b0:679:a9:9447 with SMTP id 006d021491bc7-67900a9990cmr1365449eaf.27.1771135746545; Sat, 14 Feb 2026 22:09:06 -0800 (PST) Date: Sat, 14 Feb 2026 22:09:06 -0800 In-Reply-To: <69904b0b.a70a0220.3c8f9c.008a.GAE@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <69916302.050a0220.2757fb.0030.GAE@google.com> Subject: Forwarded: Re: [syzbot] [net?] KMSAN: uninit-value in __inet_bind From: syzbot To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" For archival purposes, forwarding an incoming command email to linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com. *** Subject: Re: [syzbot] [net?] KMSAN: uninit-value in __inet_bind Author: tabreztalks@gmail.com #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git main From 42a8555a679994cc8113267b7ba08af054a48852 Mon Sep 17 00:00:00 2001 From: Tabrez Ahmed Date: Sun, 15 Feb 2026 11:24:13 +0530 Subject: [PATCH net] rds: tcp: fix uninit-value in __inet_bind KMSAN reported an uninit-value access in __inet_bind() when binding an RDS TCP socket. The uninitialized memory originates from rds_tcp_conn_alloc(), which uses kmem_cache_alloc() to allocate the rds_tcp_connection structure. The structure is not zero-initialized, leaving random data in its fields. When the networking stack later tries to bind the socket using these dirty values, KMSAN flags the uninitialized access. Fix this by using kmem_cache_zalloc() instead of kmem_cache_alloc() to ensure the structure is zeroed out upon allocation. Reported-by: syzbot+aae646f09192f72a68dc@syzkaller.appspotmail.com Closes: https://syzkaller.appspot.com/bug?extid=3Daae646f09192f72a68dc Fixes: 70041088e3b9 ("RDS: Add TCP transport to RDS") Signed-off-by: Tabrez Ahmed --- net/rds/tcp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/net/rds/tcp.c b/net/rds/tcp.c index 45484a93d75f..04f310255692 100644 --- a/net/rds/tcp.c +++ b/net/rds/tcp.c @@ -373,7 +373,7 @@ static int rds_tcp_conn_alloc(struct rds_connection *co= nn, gfp_t gfp) int ret =3D 0; =20 for (i =3D 0; i < RDS_MPATH_WORKERS; i++) { - tc =3D kmem_cache_alloc(rds_tcp_conn_slab, gfp); + tc =3D kmem_cache_zalloc(rds_tcp_conn_slab, gfp); if (!tc) { ret =3D -ENOMEM; goto fail; --=20 2.43.0