[v5.15] WARNING in ieee80211_ibss_csa_beacon (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1638a8a2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9e47345638b85bd0
dashboard link: https://syzkaller.appspot.com/bug?extid=a39e6103721cc1109d3d
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7ab49562317a/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e847ec1e38d3/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/263158c6371c/Image-c7964837.gz.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 8285 at net/mac80211/ibss.c:503 ieee80211_ibss_csa_beacon+0x4e4/0x590 net/mac80211/ibss.c:503
Modules linked in:
CPU: 1 PID: 8285 Comm: kworker/u4:11 Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Workqueue: phy4 ieee80211_csa_finalize_work
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ieee80211_ibss_csa_beacon+0x4e4/0x590 net/mac80211/ibss.c:503
lr : ieee80211_ibss_csa_beacon+0x4e4/0x590 net/mac80211/ibss.c:503
sp : ffff8000202c79c0
x29: ffff8000202c79d0 x28: 1fffe0001d43b251 x27: dfff800000000000
x26: 0000000000000000 x25: ffff0000ea1d9b08 x24: ffff0000dc8c05c0
x23: ffff0000ea1d9288 x22: ffff0000ea1d9b18 x21: 0000000000000002
x20: ffff0000ea1d8c80 x19: 0000000000000000 x18: 0000000000000201
x17: 0000000000000000 x16: ffff8000082c0bc8 x15: 0000000000000003
x14: 0000000000ff0100 x13: ffffffffffffffff x12: 0000000000ff0100
x11: 0000000000000000 x10: 0000000000000000 x9 : ffff800010afbff0
x8 : ffff0000db358000 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000010
x2 : 0000000000000006 x1 : ffff80001131b080 x0 : 0000000000000000
Call trace:
ieee80211_ibss_csa_beacon+0x4e4/0x590 net/mac80211/ibss.c:503
ieee80211_ibss_finish_csa+0x228/0x314 net/mac80211/ibss.c:559
ieee80211_set_after_csa_beacon net/mac80211/cfg.c:3188 [inline]
__ieee80211_csa_finalize net/mac80211/cfg.c:3244 [inline]
ieee80211_csa_finalize+0x3bc/0xcc4 net/mac80211/cfg.c:3267
ieee80211_csa_finalize_work+0xdc/0x128 net/mac80211/cfg.c:3292
process_one_work+0x79c/0x1140 kernel/workqueue.c:2310
worker_thread+0x8f4/0x101c kernel/workqueue.c:2457
kthread+0x374/0x454 kernel/kthread.c:334
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:855
irq event stamp: 99872
hardirqs last enabled at (99871): [<ffff80000819dc64>] __local_bh_enable_ip+0x1f8/0x380 kernel/softirq.c:406
hardirqs last disabled at (99872): [<ffff8000111b7ff8>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (99870): [<ffff80001096c8dc>] spin_unlock_bh include/linux/spinlock.h:408 [inline]
softirqs last enabled at (99870): [<ffff80001096c8dc>] cfg80211_get_bss+0x6d4/0xc68 net/wireless/scan.c:1547
softirqs last disabled at (99868): [<ffff80001096c328>] spin_lock_bh include/linux/spinlock.h:368 [inline]
softirqs last disabled at (99868): [<ffff80001096c328>] cfg80211_get_bss+0x120/0xc68 net/wireless/scan.c:1521
---[ end trace a183b04b81ef4e6f ]---
wlan1: failed to finalize CSA, disconnecting


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