[v6.1] WARNING in ieee80211_request_ibss_scan

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 8e60a714ba3b Linux 6.1.132
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14764404580000
kernel config: https://syzkaller.appspot.com/x/.config?x=14036d226c9c97a0
dashboard link: https://syzkaller.appspot.com/bug?extid=93c6f86eb2bbd45d9861
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/015af6f03147/disk-8e60a714.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4dd00fc87c24/vmlinux-8e60a714.xz
kernel image: https://storage.googleapis.com/syzbot-assets/318920d71f18/Image-8e60a714.gz.xz

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

wlan1: Trigger new scan to find an IBSS to join
------------[ cut here ]------------
WARNING: CPU: 1 PID: 4437 at net/mac80211/scan.c:1225 ieee80211_request_ibss_scan+0x594/0x610 net/mac80211/scan.c:1225
Modules linked in:
CPU: 1 PID: 4437 Comm: kworker/u4:11 Not tainted 6.1.132-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Workqueue: phy4 ieee80211_iface_work
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ieee80211_request_ibss_scan+0x594/0x610 net/mac80211/scan.c:1225
lr : ieee80211_request_ibss_scan+0x594/0x610 net/mac80211/scan.c:1225
sp : ffff8000216378a0
x29: ffff8000216378e0 x28: ffff0000c42b8ee0 x27: 0000000000000006
x26: ffff0000c42bab70 x25: 0000000000000000 x24: dfff800000000000
x23: ffff0000c42bd238 x22: ffff0000c42b8930 x21: 0000000000000c80
x20: 1fffe000188571dc x19: 0000000000000000 x18: 0000000000000150
x17: 0000000000000000 x16: ffff8000084f3ce0 x15: 0000000000000000
x14: 1ffff00002b600b2 x13: dfff800000000000 x12: 0000000000000001
x11: 0000000000ff0100 x10: 0000000000000000 x9 : ffff800011bc0a44
x8 : ffff0000d5869bc0 x7 : ffff800011bc0528 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff8000082f8b34
x2 : ffff0000d5869bc0 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
ieee80211_request_ibss_scan+0x594/0x610 net/mac80211/scan.c:1225
ieee80211_sta_find_ibss net/mac80211/ibss.c:1504 [inline]
ieee80211_ibss_work+0xc6c/0x1230 net/mac80211/ibss.c:1705
ieee80211_iface_work+0x9e0/0xa90 net/mac80211/iface.c:1744
process_one_work+0x804/0x1484 kernel/workqueue.c:2292
worker_thread+0x8e4/0xfec kernel/workqueue.c:2439
kthread+0x250/0x2d8 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:864
irq event stamp: 10233736
hardirqs last enabled at (10233735): [<ffff80000834060c>] __up_console_sem+0xb4/0x100 kernel/printk/printk.c:261
hardirqs last disabled at (10233736): [<ffff8000123244cc>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (10233724): [<ffff800011a22570>] spin_unlock_bh include/linux/spinlock.h:396 [inline]
softirqs last enabled at (10233724): [<ffff800011a22570>] cfg80211_get_bss+0x4a4/0x8c0 net/wireless/scan.c:1564
softirqs last disabled at (10233722): [<ffff800011a22214>] spin_lock_bh include/linux/spinlock.h:356 [inline]
softirqs last disabled at (10233722): [<ffff800011a22214>] cfg80211_get_bss+0x148/0x8c0 net/wireless/scan.c:1538
---[ end trace 0000000000000000 ]---
IPv6: ADDRCONF(NETDEV_CHANGE): vxcan1: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): vxcan0: link becomes ready
netdevsim netdevsim3 netdevsim3 (unregistering): unset [1, 0] type 2 family 0 port 6081 - 0


---
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