Hello,
syzbot found the following issue on:
HEAD commit: f6e38ae624cf Linux 6.1.158
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=1356af42580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=7eb38bd5021fec61
dashboard link:
https://syzkaller.appspot.com/bug?extid=d8e4b8832a9cad004b9f
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/2b7003e2661d/disk-f6e38ae6.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/0696cea8d016/vmlinux-f6e38ae6.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/6b7a89e636d7/bzImage-f6e38ae6.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+d8e4b8...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 4317 at net/mac80211/ocb.c:64 ieee80211_ocb_rx_no_sta+0x574/0x650 net/mac80211/ocb.c:64
Modules linked in:
CPU: 1 PID: 4317 Comm: kworker/1:5 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Workqueue: mld mld_ifc_work
RIP: 0010:ieee80211_ocb_rx_no_sta+0x574/0x650 net/mac80211/ocb.c:64
Code: c3 40 09 00 00 48 c7 c7 40 7f a7 8b 48 89 de 4c 89 fa 48 83 c4 10 5b 41 5c 41 5d 41 5e 41 5f 5d e9 81 84 61 00 e8 2c 95 d5 f7 <0f> 0b 48 83 c4 10 5b 41 5c 41 5d 41 5e 41 5f 5d e9 c7 00 00 00 44
RSP: 0018:ffffc900001e0838 EFLAGS: 00010246
RAX: ffffffff89ab4134 RBX: ffff888057b10c80 RCX: ffff888018691dc0
RDX: 0000000000000100 RSI: 0000000000000001 RDI: 0000000000000000
RBP: 0000000000000000 R08: dffffc0000000000 R09: fffffbfff215c449
R10: fffffbfff215c449 R11: 1ffffffff215c448 R12: ffffffff89ab3c67
R13: ffff88802ef70e80 R14: 0000000000000001 R15: ffff888054e8f03a
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2f91dff8 CR3: 00000000186d0000 CR4: 00000000003526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
ieee80211_accept_frame net/mac80211/rx.c:4349 [inline]
ieee80211_prepare_and_rx_handle+0x3d8d/0x6240 net/mac80211/rx.c:4877
__ieee80211_rx_handle_packet net/mac80211/rx.c:5180 [inline]
ieee80211_rx_list+0x24d8/0x2d00 net/mac80211/rx.c:5306
ieee80211_rx_napi+0x1a6/0x3c0 net/mac80211/rx.c:5329
ieee80211_rx include/net/mac80211.h:4846 [inline]
ieee80211_handle_queued_frames+0x105/0x1b0 net/mac80211/main.c:317
tasklet_action_common+0x298/0x400 kernel/softirq.c:826
handle_softirqs+0x2a1/0x920 kernel/softirq.c:596
do_softirq+0x13b/0x200 kernel/softirq.c:497
</IRQ>
<TASK>
__local_bh_enable_ip+0x174/0x1b0 kernel/softirq.c:421
local_bh_enable include/linux/bottom_half.h:33 [inline]
rcu_read_unlock_bh include/linux/rcupdate.h:861 [inline]
__dev_queue_xmit+0x15c9/0x3760 net/core/dev.c:4373
neigh_output include/net/neighbour.h:545 [inline]
ip6_finish_output2+0xda2/0x1590 net/ipv6/ip6_output.c:138
dst_output include/net/dst.h:453 [inline]
NF_HOOK+0x15d/0x460 include/linux/netfilter.h:302
mld_sendpack+0x893/0xe80 net/ipv6/mcast.c:1825
mld_send_cr net/ipv6/mcast.c:2126 [inline]
mld_ifc_work+0x836/0xb40 net/ipv6/mcast.c:2658
process_one_work+0x898/0x1160 kernel/workqueue.c:2292
worker_thread+0xaa2/0x1250 kernel/workqueue.c:2439
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
---
This report is generated by a bot. It may contain errors.
See
https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at
syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup