[v6.1] WARNING in ieee80211_tx_h_rate_ctrl

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f6e38ae624cf Linux 6.1.158
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1621201a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7eb38bd5021fec61
dashboard link: https://syzkaller.appspot.com/bug?extid=7fe84824873fd5712c3a
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/2b7003e2661d/disk-f6e38ae6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0696cea8d016/vmlinux-f6e38ae6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6b7a89e636d7/bzImage-f6e38ae6.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7fe848...@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: 0 PID: 46 at net/mac80211/tx.c:784 ieee80211_tx_h_rate_ctrl+0xc65/0x1730 net/mac80211/tx.c:777
Modules linked in:
CPU: 0 PID: 46 Comm: kworker/u4:3 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Workqueue: events_unbound cfg80211_wiphy_work
RIP: 0010:ieee80211_tx_h_rate_ctrl+0xc65/0x1730 net/mac80211/tx.c:777
Code: 44 24 38 8b 30 31 db 83 e6 07 0f 95 c3 31 ff e8 11 e5 e4 f7 8d 4c 5b 02 48 c7 c7 40 c5 a6 8b 4c 89 f6 4c 89 fa e8 7b 06 b1 f7 <0f> 0b 41 bf 01 00 00 00 e9 3c 03 00 00 e8 89 e1 e4 f7 e9 64 fa ff
RSP: 0000:ffffc90000b77560 EFLAGS: 00010246
RAX: c20e16e817346200 RBX: 0000000000000001 RCX: ffff88801debbb80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002
RBP: ffffc90000b776d0 R08: dffffc0000000000 R09: fffff5200016ee3d
R10: fffff5200016ee3d R11: 1ffff9200016ee3c R12: dffffc0000000000
R13: ffff88801fe5b8c0 R14: ffff888054ed55c0 R15: ffff8880785e6044
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb9540bdf98 CR3: 00000000306b3000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
invoke_tx_handlers_late+0xb6/0x1810 net/mac80211/tx.c:1885
ieee80211_tx+0x2a9/0x410 net/mac80211/tx.c:2006
__ieee80211_tx_skb_tid_band+0x4d1/0x610 net/mac80211/tx.c:5862
ieee80211_tx_skb_tid_band net/mac80211/ieee80211_i.h:2187 [inline]
ieee80211_send_scan_probe_req net/mac80211/scan.c:652 [inline]
ieee80211_scan_state_send_probe+0x560/0x930 net/mac80211/scan.c:680
ieee80211_scan_work+0x4d2/0x1bc0 net/mac80211/scan.c:1150
cfg80211_wiphy_work+0x221/0x260 net/wireless/core.c:433
process_one_work+0x898/0x1160 kernel/workqueue.c:2292
worker_thread+0xaa2/0x1250 kernel/workqueue.c:2439
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</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