[v6.6] WARNING in ieee80211_tx_h_rate_ctrl

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0a805b6ea8cd Linux 6.6.116
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14083bcd980000
kernel config: https://syzkaller.appspot.com/x/.config?x=12606d4b8832c7e4
dashboard link: https://syzkaller.appspot.com/bug?extid=35ad01f7f3622937dc14
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/13874446b4b2/disk-0a805b6e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/69a5e59e1ade/vmlinux-0a805b6e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/322c0711f976/bzImage-0a805b6e.xz

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

------------[ cut here ]------------
wlan1: Dropped data frame as no usable bitrate found while scanning and associated. Target station: 08:02:11:00:00:00 on 5 GHz band
WARNING: CPU: 1 PID: 49 at net/mac80211/tx.c:769 ieee80211_tx_h_rate_ctrl+0xc7e/0x1770 net/mac80211/tx.c:762
Modules linked in:
CPU: 1 PID: 49 Comm: kworker/u4:3 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Workqueue: events_unbound cfg80211_wiphy_work
RIP: 0010:ieee80211_tx_h_rate_ctrl+0xc7e/0x1770 net/mac80211/tx.c:762
Code: 8b 36 45 31 f6 83 e6 07 41 0f 95 c6 31 ff e8 29 8e 97 f7 43 8d 4c 76 02 48 c7 c7 e0 d3 be 8b 48 89 de 4c 89 fa e8 c2 07 62 f7 <0f> 0b 41 bf 01 00 00 00 e9 eb 02 00 00 e8 50 8a 97 f7 e9 70 fa ff
RSP: 0018:ffffc90000ba74e0 EFLAGS: 00010246
RAX: e1ddb8f777581500 RBX: ffff88801e7d95b0 RCX: ffff88801bed8000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002
RBP: ffffc90000ba7650 R08: ffffc90000ba70e7 R09: 1ffff92000174e1c
R10: dffffc0000000000 R11: fffff52000174e1d R12: dffffc0000000000
R13: ffffc90000ba7808 R14: 0000000000000001 R15: ffff8880565ae444
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000034000 CR3: 000000001c76b000 CR4: 00000000003526e0
Call Trace:
<TASK>
invoke_tx_handlers_late+0xb6/0x1810 net/mac80211/tx.c:1862
ieee80211_tx+0x2ad/0x420 net/mac80211/tx.c:1983
__ieee80211_tx_skb_tid_band+0x4d5/0x610 net/mac80211/tx.c:6081
ieee80211_tx_skb_tid_band net/mac80211/ieee80211_i.h:2276 [inline]
ieee80211_send_scan_probe_req net/mac80211/scan.c:641 [inline]
ieee80211_scan_state_send_probe+0x560/0x930 net/mac80211/scan.c:669
ieee80211_scan_work+0x4e8/0x1c30 net/mac80211/scan.c:1139
cfg80211_wiphy_work+0x225/0x260 net/wireless/core.c:437
process_one_work kernel/workqueue.c:2634 [inline]
process_scheduled_works+0xa45/0x15b0 kernel/workqueue.c:2711
worker_thread+0xa55/0xfc0 kernel/workqueue.c:2792
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</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