[v5.15] WARNING in ieee80211_request_ibss_scan (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 9eec9a14ee10 Linux 5.15.198
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15796bfc580000
kernel config: https://syzkaller.appspot.com/x/.config?x=30e28339904629ca
dashboard link: https://syzkaller.appspot.com/bug?extid=fc4e8edf133b1b2d6cf3
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/6ad9416079e2/disk-9eec9a14.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ba7fc9fdefee/vmlinux-9eec9a14.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c2319717f0e5/bzImage-9eec9a14.xz

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

wlan1: No active IBSS STAs - trying to scan for other IBSS networks with same SSID (merge)
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4394 at net/mac80211/scan.c:1219 ieee80211_request_ibss_scan+0xc7c/0xda0 net/mac80211/scan.c:1219
Modules linked in:
CPU: 0 PID: 4394 Comm: kworker/u4:8 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Workqueue: phy11 ieee80211_iface_work
RIP: 0010:ieee80211_request_ibss_scan+0xc7c/0xda0 net/mac80211/scan.c:1219
Code: 4c 89 ff e8 f6 c5 ff ff 89 c3 48 8b 7c 24 30 e8 1a 07 81 00 89 d8 48 83 c4 68 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 24 38 37 f8 <0f> 0b bb f0 ff ff ff eb d7 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 91
RSP: 0018:ffffc9000341fa00 EFLAGS: 00010293
RAX: ffffffff8941d77c RBX: ffff888077d1aa20 RCX: ffff888023823b80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: dffffc0000000000 R08: ffffc9000341f7c7 R09: 1ffff92000683ef8
R10: dffffc0000000000 R11: fffff52000683ef9 R12: ffff888077d1de10
R13: ffff888077d18de0 R14: 0000000000000001 R15: ffff88805e700c80
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000561b8d57bf10 CR3: 00000000632a4000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ieee80211_sta_merge_ibss net/mac80211/ibss.c:1318 [inline]
ieee80211_ibss_work+0xd9f/0x10e0 net/mac80211/ibss.c:1713
process_one_work+0x85f/0x1010 kernel/workqueue.c:2310
worker_thread+0xaa6/0x1290 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</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