[v6.6] WARNING in __cfg80211_ibss_joined

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c2603c511feb Linux 6.6.93
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13dcbe82580000
kernel config: https://syzkaller.appspot.com/x/.config?x=486bade17c8c30b9
dashboard link: https://syzkaller.appspot.com/bug?extid=a32e3087f66d8affe3ec
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8754f950a6e7/disk-c2603c51.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3b19332dbf63/vmlinux-c2603c51.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cb245e836038/bzImage-c2603c51.xz

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

wlan1: Trigger new scan to find an IBSS to join
------------[ cut here ]------------
WARNING: CPU: 1 PID: 8076 at net/wireless/ibss.c:37 __cfg80211_ibss_joined+0x3c2/0x430 net/wireless/ibss.c:37
Modules linked in:
CPU: 1 PID: 8076 Comm: kworker/u4:16 Not tainted 6.6.93-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Workqueue: cfg80211 cfg80211_event_work
RIP: 0010:__cfg80211_ibss_joined+0x3c2/0x430 net/wireless/ibss.c:37
Code: 00 00 00 48 3b 84 24 80 00 00 00 75 5c 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 97 b8 bc f7 0f 0b eb c3 e8 8e b8 bc f7 <0f> 0b 4c 8b 6c 24 18 eb b5 e8 80 b8 bc f7 0f 0b e9 e8 fd ff ff e8
RSP: 0018:ffffc900033a7a20 EFLAGS: 00010293
RAX: ffffffff89c8de52 RBX: dffffc0000000000 RCX: ffff888028bf8000
RDX: 0000000000000000 RSI: ffffffff8aaab2c0 RDI: ffffffff8afc6780
RBP: ffffc900033a7af8 R08: ffffffff90d8458f R09: 1ffffffff21b08b1
R10: dffffc0000000000 R11: fffffbfff21b08b2 R12: ffff888030eb4c90
R13: 1ffff92000674f4c R14: ffff88807d9035b8 R15: 000000000000000b
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c3e3879 CR3: 000000006bd92000 CR4: 00000000003506e0
DR0: 0000040000000000 DR1: 000000000000000c DR2: 0000000000000006
DR3: 0000000000000006 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
cfg80211_process_wdev_events+0x3bc/0x550 net/wireless/util.c:1071
cfg80211_process_rdev_events+0xa1/0x110 net/wireless/util.c:1099
cfg80211_event_work+0x2f/0x40 net/wireless/core.c:335
process_one_work kernel/workqueue.c:2634 [inline]
process_scheduled_works+0xa45/0x15b0 kernel/workqueue.c:2711
worker_thread+0xa55/0xfc0 kernel/workqueue.c:2792
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</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