[v5.15] WARNING in cfg80211_scan_done

Hello,

syzbot found the following issue on:

HEAD commit: 0c935c049b5c Linux 5.15.179
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=109fddb0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=bcb6af887426ce59
dashboard link: https://syzkaller.appspot.com/bug?extid=b87221e3eb1912befae2
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/75b060834e1e/disk-0c935c04.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d42b06ae465d/vmlinux-0c935c04.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d5217676cd35/bzImage-0c935c04.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

------------[ cut here ]------------
WARNING: CPU: 0 PID: 4622 at net/wireless/scan.c:1101 cfg80211_scan_done+0x33d/0x4c0
Modules linked in:
CPU: 1 PID: 4622 Comm: kworker/u4:8 Not tainted 5.15.179-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Workqueue: phy15 ieee80211_scan_work
RIP: 0010:cfg80211_scan_done+0x33d/0x4c0 net/wireless/scan.c:1100
Code: 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 cb 27 cf f7 0f 0b e9 c1 fd ff ff e8 bf 27 cf f7 0f 0b e9 12 fe ff ff e8 b3 27 cf f7 <0f> 0b e9 8d fe ff ff 89 d9 80 e1 07 38 c1 0f 8c b5 fe ff ff 48 89
RSP: 0018:ffffc9000470f960 EFLAGS: 00010293
RAX: ffffffff89b1750d RBX: ffff88801e7081b0 RCX: ffff888079ca1dc0
RDX: 0000000000000000 RSI: ffffffff8af9fa60 RDI: ffffffff8af9fa20
RBP: ffffc9000470fa30 R08: ffffffff89b172fc R09: fffffbfff1c153f6
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88801e7081b8
R13: dffffc0000000000 R14: 1ffff1100efd824d R15: ffff888077ec1200
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000056142d39e950 CR3: 0000000058d8b000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__ieee80211_scan_completed+0x511/0xa00 net/mac80211/scan.c:478
ieee80211_scan_work+0x16b/0x1d00 net/mac80211/scan.c:1163
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
kthread+0x3f6/0x4f0 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 [email protected].

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