From: syzbot <syzbot+9a4fbb77c9d4aacd3388@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Forwarded: [PATCH net] net/core : fix KMSAN: uninit value in tipc_rcv
Date: Fri, 19 Sep 2025 08:23:46 -0700 [thread overview]
Message-ID: <68cd7582.050a0220.13cd81.0001.GAE@google.com> (raw)
In-Reply-To: <6880f58e.050a0220.248954.0001.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: [PATCH net] net/core : fix KMSAN: uninit value in tipc_rcv
Author: hariconscious@gmail.com
From: HariKrishna Sagala <hariconscious@gmail.com>
syzbot KMSAN points to the unint value in the socket buffer creation.
In the skbuff.c, kmalloc_reserve API takes gfp flags option, appended the
flag "GFP_ZERO" to the existing flags to get the zeroed buffer.
Reported-by:syzbot+9a4fbb77c9d4aacd3388@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=9a4fbb77c9d4aacd3388
Signed-off-by: HariKrishna Sagala <hariconscious@gmail.com>
---
#syz test
net/core/skbuff.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/net/core/skbuff.c b/net/core/skbuff.c
index ee0274417948..2308ebf99bbd 100644
--- a/net/core/skbuff.c
+++ b/net/core/skbuff.c
@@ -573,6 +573,7 @@ static void *kmalloc_reserve(unsigned int *size, gfp_t flags, int node,
void *obj;
obj_size = SKB_HEAD_ALIGN(*size);
+ flags |= __GFP_ZERO;
if (obj_size <= SKB_SMALL_HEAD_CACHE_SIZE &&
!(flags & KMALLOC_NOT_NORMAL_BITS)) {
obj = kmem_cache_alloc_node(net_hotdata.skb_small_head_cache,
--
2.43.0
next prev parent reply other threads:[~2025-09-19 15:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 14:45 [syzbot] [tipc?] KMSAN: uninit-value in tipc_rcv (2) syzbot
2025-08-03 9:39 ` syzbot
2025-09-19 15:23 ` syzbot [this message]
2025-09-20 17:01 ` Forwarded: [PATCH v2 net] net/core : fix KMSAN: uninit value in tipc_rcv syzbot
2025-11-07 6:06 ` Forwarded: [PATCH] net: core: fix KMSAN: unint " syzbot
2025-11-07 7:15 ` syzbot
2025-11-07 10:19 ` syzbot
2025-11-18 12:37 ` syzbot
2025-11-22 3:37 ` syzbot
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=68cd7582.050a0220.13cd81.0001.GAE@google.com \
--to=syzbot+9a4fbb77c9d4aacd3388@syzkaller.appspotmail.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.