[syzbot] [wireless?] WARNING in cfg80211_cac_event
From: syzbot <hidden>
Date: 2026-10-26 01:32:44
Also in:
linux-wireless, lkml
Hello, syzbot found the following issue on: HEAD commit: 734bef548a96 Merge tag 'net-next-7.4' of git://git.kernel... git tree: net-next console output: https://syzkaller.appspot.com/x/log.txt?x=12a55469580000 kernel config: https://syzkaller.appspot.com/x/.config?x=d0f4f48df8e34eb3 dashboard link: https://syzkaller.appspot.com/bug?extid=3df76a08d929e91e5327 compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/585a51a9cc57/disk-734bef54.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/b2888e6093ab/vmlinux-734bef54.xz kernel image: https://storage.googleapis.com/syzbot-assets/74d0b6ec60eb/bzImage-734bef54.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: <redacted> ------------[ cut here ]------------ !time_after_eq(jiffies, timeout) WARNING: net/wireless/mlme.c:1309 at cfg80211_cac_event+0x45b/0x6e0 net/wireless/mlme.c:1309, CPU#1: kworker/u8:3/2120 Modules linked in: CPU: 1 UID: 0 PID: 2120 Comm: kworker/u8:3 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/07/2026 Workqueue: events_unbound cfg80211_wiphy_work RIP: 0010:cfg80211_cac_event+0x45b/0x6e0 net/wireless/mlme.c:1309 Code: fc ff ff e8 67 a8 7d f6 90 0f 0b 90 eb c8 e8 5c a8 7d f6 48 8d 3d 85 18 43 06 67 48 0f b9 3a e9 35 fd ff ff e8 46 a8 7d f6 90 <0f> 0b 90 e9 82 fe ff ff 89 d9 80 e1 07 fe c1 38 c1 0f 8c 24 fc ff RSP: 0000:ffffc9000328f918 EFLAGS: 00010293 RAX: ffffffff8b4abdda RBX: 0000000100010317 RCX: ffff888031c13e80 RDX: 0000000000000000 RSI: ffffffffffffffff RDI: 0000000000000000 RBP: 0000000100011a86 R08: ffff888031c13e80 R09: 0000000000000003 R10: 0000000000000005 R11: 0000000000000000 R12: ffff8880569213e8 R13: dffffc0000000000 R14: 0000000100011a87 R15: 1ffff1100ad2427d FS: 0000000000000000(0000) GS:ffff888123b6b000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ffd8c6a5cdc CR3: 000000007562a000 CR4: 00000000003526f0 Call Trace: <TASK> ieee80211_dfs_cac_timer_work+0x264/0x380 net/mac80211/mlme.c:3995 cfg80211_wiphy_work+0x29e/0x420 net/wireless/core.c:610 process_one_work kernel/workqueue.c:3495 [inline] process_scheduled_works+0xc3d/0x1630 kernel/workqueue.c:3578 worker_thread+0xa47/0xfb0 kernel/workqueue.c:3659 kthread+0x38b/0x480 kernel/kthread.c:436 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 </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 syzkaller@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