[v5.15] WARNING in ieee80211_mgd_probe_ap_send (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: aabd761612db Linux 5.15.215
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=165f82c6580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f161cbc9aef65db0
dashboard link: https://syzkaller.appspot.com/bug?extid=b7eb5454d1bbd0ad507f
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f636f56d3662/disk-aabd7616.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f1a46620f40c/vmlinux-aabd7616.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9b78bb48b022/bzImage-aabd7616.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 4905 at net/mac80211/mlme.c:2557 ieee80211_mgd_probe_ap_send+0x5aa/0x670 net/mac80211/mlme.c:2557
Modules linked in:
CPU: 0 PID: 4905 Comm: kworker/u4:14 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Workqueue: phy12 ieee80211_beacon_connection_loss_work
RIP: 0010:ieee80211_mgd_probe_ap_send+0x5aa/0x670 net/mac80211/mlme.c:2557
Code: fc 8e 1b f8 48 8b 3c 24 48 81 c7 88 0d 00 00 4c 89 f6 48 83 c4 20 5b 41 5c 41 5d 41 5e 41 5f 5d e9 ab ad 0a f8 e8 d6 8e 1b f8 <0f> 0b e9 74 fb ff ff e8 ca 8e 1b f8 0f 0b e9 42 ff ff ff e8 be 8e
RSP: 0018:ffffc900033ffbb0 EFLAGS: 00010293
RAX: ffffffff895d6dda RBX: ffff88805ed90c80 RCX: ffff888073f08000
RDX: 0000000000000000 RSI: ffffffff8a2b3e80 RDI: ffffffff8a7a4200
RBP: 1ffff1100bdb2251 R08: ffffffff8d8b0def R09: 1ffffffff1b161bd
R10: dffffc0000000000 R11: fffffbfff1b161be R12: ffff88805ff2e8b8
R13: ffff88805ed91288 R14: 0000000000000002 R15: ffff88805ed91c78
FS: 0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000007205b000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ieee80211_mgd_probe_ap+0x2b8/0x320 net/mac80211/mlme.c:2640
process_one_work+0x867/0xff0 kernel/workqueue.c:2310
worker_thread+0xad7/0x12a0 kernel/workqueue.c:2457
kthread+0x42e/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