From: syzbot <syzbot+878ddc3962f792e9af59@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, listout@listout.xyz,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [wireless?] KMSAN: uninit-value in cfg80211_classify8021d
Date: Tue, 21 Oct 2025 21:29:02 -0700 [thread overview]
Message-ID: <68f85d8e.a70a0220.3bf6c6.000f.GAE@google.com> (raw)
In-Reply-To: <upjjyn33ilectirauf64oi6xxes7esatropyat6jtah7m5bupj@oeg67dns7bt6>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
KMSAN: uninit-value in cfg80211_classify8021d
RBP: 00007f2e3fe11f91 R08: 00002000000001c0 R09: 0000000000000014
R10: 0000000000000040 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f2e3ffe6038 R14: 00007f2e3ffe5fa0 R15: 00007fff6dff3448
</TASK>
---[ end trace 0000000000000000 ]---
=====================================================
BUG: KMSAN: uninit-value in cfg80211_classify8021d+0xc2f/0x1580 net/wireless/util.c:1035
cfg80211_classify8021d+0xc2f/0x1580 net/wireless/util.c:1035
ieee80211_select_queue+0x37a/0x9e0 net/mac80211/wme.c:180
__ieee80211_subif_start_xmit+0x60f/0x1d90 net/mac80211/tx.c:4304
ieee80211_subif_start_xmit+0xa8/0x6d0 net/mac80211/tx.c:4538
__netdev_start_xmit include/linux/netdevice.h:5248 [inline]
netdev_start_xmit include/linux/netdevice.h:5257 [inline]
xmit_one net/core/dev.c:3845 [inline]
dev_hard_start_xmit+0x22f/0xa30 net/core/dev.c:3861
__dev_queue_xmit+0x3c51/0x5e60 net/core/dev.c:4763
dev_queue_xmit include/linux/netdevice.h:3365 [inline]
packet_xmit+0x8f/0x710 net/packet/af_packet.c:275
packet_snd net/packet/af_packet.c:3076 [inline]
packet_sendmsg+0x9173/0xa2a0 net/packet/af_packet.c:3108
sock_sendmsg_nosec net/socket.c:727 [inline]
__sock_sendmsg+0x333/0x3d0 net/socket.c:742
__sys_sendto+0x593/0x720 net/socket.c:2244
__do_sys_sendto net/socket.c:2251 [inline]
__se_sys_sendto net/socket.c:2247 [inline]
__x64_sys_sendto+0x130/0x200 net/socket.c:2247
x64_sys_call+0x3924/0x3e30 arch/x86/include/generated/asm/syscalls_64.h:45
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xd9/0xfa0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
Uninit was created at:
slab_post_alloc_hook mm/slub.c:4969 [inline]
slab_alloc_node mm/slub.c:5272 [inline]
kmem_cache_alloc_node_noprof+0x989/0x16b0 mm/slub.c:5324
kmalloc_reserve+0x13c/0x4b0 net/core/skbuff.c:579
__alloc_skb+0x347/0x7d0 net/core/skbuff.c:670
alloc_skb include/linux/skbuff.h:1383 [inline]
alloc_skb_with_frags+0xc5/0xa60 net/core/skbuff.c:6671
sock_alloc_send_pskb+0xacc/0xc60 net/core/sock.c:2965
packet_alloc_skb net/packet/af_packet.c:2926 [inline]
packet_snd net/packet/af_packet.c:3019 [inline]
packet_sendmsg+0x743d/0xa2a0 net/packet/af_packet.c:3108
sock_sendmsg_nosec net/socket.c:727 [inline]
__sock_sendmsg+0x333/0x3d0 net/socket.c:742
__sys_sendto+0x593/0x720 net/socket.c:2244
__do_sys_sendto net/socket.c:2251 [inline]
__se_sys_sendto net/socket.c:2247 [inline]
__x64_sys_sendto+0x130/0x200 net/socket.c:2247
x64_sys_call+0x3924/0x3e30 arch/x86/include/generated/asm/syscalls_64.h:45
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xd9/0xfa0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
CPU: 1 UID: 0 PID: 6494 Comm: syz.0.17 Tainted: G W syzkaller #0 PREEMPT(none)
Tainted: [W]=WARN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
=====================================================
Tested on:
commit: 552c5071 Merge tag 'vfio-v6.18-rc3' of https://github...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=101e8d2f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=bbd3e7f3c2e28265
dashboard link: https://syzkaller.appspot.com/bug?extid=878ddc3962f792e9af59
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=1328d734580000
next parent reply other threads:[~2025-10-22 4:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <upjjyn33ilectirauf64oi6xxes7esatropyat6jtah7m5bupj@oeg67dns7bt6>
2025-10-22 4:29 ` syzbot [this message]
[not found] <CAMz+-CMWQU1XQeyqT33fX1tiyiJnG=tk2kTn3e5-wuWp0TR4aQ@mail.gmail.com>
2025-11-12 18:16 ` [syzbot] [wireless?] KMSAN: uninit-value in cfg80211_classify8021d syzbot
[not found] <CAMz+-CPeLokTi6gfV-tX8Eb4DEaYJ6fW+8swtB+y2VY3SEKwqw@mail.gmail.com>
2025-11-12 16:22 ` syzbot
[not found] <CAMz+-CPAeuET_d_2b_tNEdNiVT1R7mzLYWih+nKa8=Dp0WjqHA@mail.gmail.com>
2025-11-12 14:02 ` syzbot
2025-11-12 14:49 ` Ranganath V N
2025-11-12 15:33 ` syzbot
[not found] <CAMz+-CMX9fRx=L+r2AwvfMK6NhiFJ50fQQtp=Wm+jR1hPn+GWw@mail.gmail.com>
2025-11-11 19:55 ` syzbot
[not found] <CAMz+-CPTNkvMjNYNfEs3vDz=cyJ7MNwciJCpu7sGUbHbd-Qz7Q@mail.gmail.com>
2025-11-01 18:10 ` syzbot
[not found] <e22jzcxyc6o2gng7lx6bskmpxhejatjm7x7q3rzlk33ji6dqhh@r4jqd66ocktj>
2025-10-21 14:17 ` syzbot
2025-10-20 21:07 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=68f85d8e.a70a0220.3bf6c6.000f.GAE@google.com \
--to=syzbot+878ddc3962f792e9af59@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=listout@listout.xyz \
--cc=syzkaller-bugs@googlegroups.com \
/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