Hello, syzbot found the following issue on: HEAD commit: 234cb065ad82 Add linux-next specific files for 20240605 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=160c62ce980000 kernel config: https://syzkaller.appspot.com/x/.config?x=fc762e458631913 dashboard link: https://syzkaller.appspot.com/bug?extid=161cd7b97ad2b6e21fb6 compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/f0492dc0386a/disk-234cb065.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/490224339088/vmlinux-234cb065.xz kernel image: https://storage.googleapis.com/syzbot-assets/5843c0673606/bzImage-234cb065.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+161cd7b97ad2b6e21fb6@xxxxxxxxxxxxxxxxxxxxxxxxx warning: `syz-executor.4' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211 ------------[ cut here ]------------ UBSAN: array-index-out-of-bounds in net/wireless/scan.c:3461:8 index 33 is out of range for type 'struct iw_freq[32]' CPU: 1 PID: 7326 Comm: syz-executor.4 Tainted: G W 6.10.0-rc2-next-20240605-syzkaller #0 Tainted: [W]=WARN Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024 Call Trace: <TASK> __dump_stack lib/dump_stack.c:91 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:117 ubsan_epilogue lib/ubsan.c:231 [inline] __ubsan_handle_out_of_bounds+0x121/0x150 lib/ubsan.c:429 cfg80211_wext_siwscan+0x56d/0x10d0 net/wireless/scan.c:3461 ioctl_standard_iw_point+0x788/0xcb0 net/wireless/wext-core.c:867 ioctl_standard_call+0xc7/0x290 net/wireless/wext-core.c:1052 wext_ioctl_dispatch+0x58e/0x640 net/wireless/wext-core.c:1016 wext_handle_ioctl+0x15f/0x270 net/wireless/wext-core.c:1077 sock_ioctl+0x17f/0x8e0 net/socket.c:1275 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f14b5e7cee9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f14b6be20c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f14b5fb3f80 RCX: 00007f14b5e7cee9 RDX: 0000000020000000 RSI: 0000000000008b18 RDI: 0000000000000005 RBP: 00007f14b5eda6fe R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007f14b5fb3f80 R15: 00007ffc59f64db8 </TASK> ---[ end trace ]--- --- 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@xxxxxxxxxxxxxxxx. 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
