Hello, syzbot found the following issue on: HEAD commit: 0b4f5add9fa5 Merge branch 'mlx5-fixes' git tree: net console output: https://syzkaller.appspot.com/x/log.txt?x=16d3e7dc980000 kernel config: https://syzkaller.appspot.com/x/.config?x=48c05addbb27f3b0 dashboard link: https://syzkaller.appspot.com/bug?extid=d6eb9cee2885ec06f5e3 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/012c6c28629f/disk-0b4f5add.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/a95912632824/vmlinux-0b4f5add.xz kernel image: https://storage.googleapis.com/syzbot-assets/4bc604c85096/bzImage-0b4f5add.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+d6eb9cee2885ec06f5e3@xxxxxxxxxxxxxxxxxxxxxxxxx ------------[ cut here ]------------ WARNING: CPU: 1 PID: 2887 at net/wireless/sme.c:846 __cfg80211_connect_result+0x19ea/0x21d0 net/wireless/sme.c:846 Modules linked in: CPU: 1 PID: 2887 Comm: kworker/u8:13 Not tainted 6.9.0-syzkaller-12082-g0b4f5add9fa5 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024 Workqueue: cfg80211 cfg80211_event_work RIP: 0010:__cfg80211_connect_result+0x19ea/0x21d0 net/wireless/sme.c:846 Code: a3 00 89 c3 31 ff 89 c6 e8 83 eb b3 f6 85 db 74 29 e8 5a 17 9a f6 84 c0 74 27 e8 31 e7 b3 f6 e9 84 00 00 00 e8 27 e7 b3 f6 90 <0f> 0b 90 4c 89 ff 4c 89 f6 e8 68 23 00 00 eb 91 e8 11 e7 b3 f6 eb RSP: 0018:ffffc90009f579e0 EFLAGS: 00010293 RAX: ffffffff8ae22d59 RBX: 0000000000000000 RCX: ffff88802b8c8000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc90009f57b00 R08: ffffffff8ae22929 R09: 1ffffffff25f4abd R10: dffffc0000000000 R11: fffffbfff25f4abe R12: ffff88807cb8f898 R13: dffffc0000000000 R14: ffff88807cb8f818 R15: ffff88805ff1f000 FS: 0000000000000000(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000001b3362a000 CR3: 00000000732a4000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> cfg80211_process_wdev_events+0x356/0x510 net/wireless/util.c:1105 cfg80211_process_rdev_events+0xac/0x110 net/wireless/util.c:1147 cfg80211_event_work+0x2f/0x40 net/wireless/core.c:335 process_one_work kernel/workqueue.c:3231 [inline] process_scheduled_works+0xa2c/0x1830 kernel/workqueue.c:3312 worker_thread+0x86d/0xd70 kernel/workqueue.c:3393 kthread+0x2f0/0x390 kernel/kthread.c:389 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </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@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
