[v5.15] WARNING in ieee80211_ibss_csa_beacon (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4735586da88e Linux 5.15.176
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1496cab0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8c3b695ffd9247a0
dashboard link: https://syzkaller.appspot.com/bug?extid=4b2ba5be5f7ed9cf598d
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/44a9faa53b37/disk-4735586d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2e4ec21926b2/vmlinux-4735586d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f96f554b1d28/bzImage-4735586d.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 14769 at net/mac80211/ibss.c:503 ieee80211_ibss_csa_beacon+0x572/0x620
Modules linked in:
CPU: 1 PID: 14769 Comm: kworker/u4:9 Not tainted 5.15.176-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
Workqueue: phy33 ieee80211_csa_finalize_work
RIP: 0010:ieee80211_ibss_csa_beacon+0x572/0x620 net/mac80211/ibss.c:503
Code: f7 c6 05 9e 1c 2a 04 01 48 c7 c7 d0 75 b8 8b be 01 02 00 00 48 c7 c2 60 76 b8 8b e8 78 7c 96 f7 e9 6a fe ff ff e8 9e d4 b3 f7 <0f> 0b b8 ea ff ff ff e9 7a ff ff ff e8 8d d4 b3 f7 0f 0b e9 f5 fa
RSP: 0018:ffffc900031cfb68 EFLAGS: 00010293
RAX: ffffffff89ccb042 RBX: ffff8880779bb710 RCX: ffff88805c193b80
RDX: 0000000000000000 RSI: ffffffff8aab2b80 RDI: ffffffff8af9f340
RBP: ffff88805402dae2 R08: dffffc0000000000 R09: fffffbfff213143a
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88805402dae8
R13: ffff8880779b85c0 R14: ffff88805402cc80 R15: ffff88805402db08
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c3a41c4 CR3: 00000000252d2000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ieee80211_set_after_csa_beacon net/mac80211/cfg.c:3188 [inline]
__ieee80211_csa_finalize net/mac80211/cfg.c:3244 [inline]
ieee80211_csa_finalize+0x472/0xb10 net/mac80211/cfg.c:3267
ieee80211_csa_finalize_work+0xf8/0x140 net/mac80211/cfg.c:3292
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 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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.