[v6.1] WARNING in ieee80211_rx_list (3)

0 views
Skip to first unread message

syzbot

unread,
2:34 PM (2 hours ago) 2:34 PM
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: ad16b162f21d Linux 6.1.172
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=176f2e36580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f0605c5af04d7603
dashboard link: https://syzkaller.appspot.com/bug?extid=63e1c0a0f804a765b72a
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/cbdf9b724121/disk-ad16b162.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f0af3cbf0ddc/vmlinux-ad16b162.xz
kernel image: https://storage.googleapis.com/syzbot-assets/19e5f4832ee2/bzImage-ad16b162.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+63e1c0...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 1 PID: 21 at net/mac80211/rx.c:5233 ieee80211_rx_list+0x2310/0x2e60 net/mac80211/rx.c:5233
Modules linked in:
CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
RIP: 0010:ieee80211_rx_list+0x2310/0x2e60 net/mac80211/rx.c:5233
Code: 0f 0b e9 3c e1 ff ff e8 7e 2f d5 f7 0f 0b eb 1c e8 75 2f d5 f7 eb 15 e8 6e 2f d5 f7 eb 0e e8 67 2f d5 f7 eb 07 e8 60 2f d5 f7 <0f> 0b 4c 8b 7c 24 08 e9 0d e1 ff ff e8 4f 2f d5 f7 48 c7 44 24 58
RSP: 0018:ffffc900001b7880 EFLAGS: 00010246
RAX: ffffffff89ad45f0 RBX: ffff8880650308e8 RCX: ffff888017751dc0
RDX: 0000000000000100 RSI: 0000000000000000 RDI: 0000000000000005
RBP: ffffc900001b7a90 R08: dffffc0000000000 R09: 1ffffffff215f248
R10: dffffc0000000000 R11: fffffbfff215f249 R12: 1ffff1100cdfbe1b
R13: dffffc0000000000 R14: ffff8880650315bd R15: ffff888065033348
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffeb8e260e8 CR3: 0000000030015000 CR4: 00000000003506e0
DR0: 0000200000000300 DR1: 0000200000000300 DR2: 0000000000000000
DR3: 0000000000008d24 DR6: 00000000ffff0ff0 DR7: 0000000000000600
Call Trace:
<TASK>
ieee80211_rx_napi+0x1ae/0x3d0 net/mac80211/rx.c:5338
ieee80211_rx include/net/mac80211.h:4849 [inline]
ieee80211_handle_queued_frames+0x105/0x1b0 net/mac80211/main.c:317
tasklet_action_common+0x2fe/0x4d0 kernel/softirq.c:827
handle_softirqs+0x2a1/0x930 kernel/softirq.c:596
run_ksoftirqd+0xa4/0x100 kernel/softirq.c:968
smpboot_thread_fn+0x64a/0xa40 kernel/smpboot.c:164
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
Reply all
Reply to author
Forward
0 new messages