[v6.1] WARNING in rate_control_rate_init

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 69e434a1cb21 Linux 6.1.63
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15791be8e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=cb9f1be873e58e15
dashboard link: https://syzkaller.appspot.com/bug?extid=0cb30b32850d5765f59c
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/042eff9b94a8/disk-69e434a1.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/dce36c399f65/vmlinux-69e434a1.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c40f6d7a93b8/bzImage-69e434a1.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 12465 at net/mac80211/rate.c:48 rate_control_rate_init+0x57a/0x5e0
Modules linked in:
CPU: 0 PID: 12465 Comm: syz-executor.4 Not tainted 6.1.63-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
RIP: 0010:rate_control_rate_init+0x57a/0x5e0 net/mac80211/rate.c:48
Code: 01 00 00 be 08 00 00 00 e8 43 f4 d8 f7 f0 41 80 8d 82 01 00 00 20 48 83 c4 20 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 66 9b 81 f7 <0f> 0b 48 83 c4 20 5b 41 5c 41 5d 41 5e 41 5f 5d eb 54 89 e9 80 e1
RSP: 0018:ffffc900038af0f8 EFLAGS: 00010283
RAX: ffffffff8a08f48a RBX: ffff888079966ae8 RCX: 0000000000040000
RDX: ffffc9000cc39000 RSI: 00000000000007e5 RDI: 00000000000007e6
RBP: 0000000000000001 R08: ffffffff8a08f0fe R09: fffffbfff2091a45
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88807c710e80
R13: ffff888014694000 R14: 1ffff110028d280a R15: 0000000000000000
FS: 00007f4517b576c0(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b32a21000 CR3: 0000000052e29000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
sta_apply_auth_flags+0x1b6/0x410 net/mac80211/cfg.c:1580
sta_apply_parameters+0xda6/0x14a0 net/mac80211/cfg.c:1908
ieee80211_add_station+0x342/0x560 net/mac80211/cfg.c:1973
rdev_add_station+0x121/0x2f0 net/wireless/rdev-ops.h:201
nl80211_new_station+0x1d33/0x24f0 net/wireless/nl80211.c:7402
genl_family_rcv_msg_doit net/netlink/genetlink.c:756 [inline]
genl_family_rcv_msg net/netlink/genetlink.c:833 [inline]
genl_rcv_msg+0xc1a/0xf70 net/netlink/genetlink.c:850
netlink_rcv_skb+0x1cd/0x410 net/netlink/af_netlink.c:2508
genl_rcv+0x24/0x40 net/netlink/genetlink.c:861
netlink_unicast_kernel net/netlink/af_netlink.c:1326 [inline]
netlink_unicast+0x7d8/0x970 net/netlink/af_netlink.c:1352
netlink_sendmsg+0xa26/0xd60 net/netlink/af_netlink.c:1874
sock_sendmsg_nosec net/socket.c:716 [inline]
__sock_sendmsg net/socket.c:728 [inline]
____sys_sendmsg+0x59e/0x8f0 net/socket.c:2499
___sys_sendmsg net/socket.c:2553 [inline]
__sys_sendmsg+0x2a9/0x390 net/socket.c:2582
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f4516e7cae9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f4517b570c8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007f4516f9bf80 RCX: 00007f4516e7cae9
RDX: 0000000000000000 RSI: 00000000200004c0 RDI: 0000000000000003
RBP: 00007f4516ec847a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f4516f9bf80 R15: 00007fffc4fd8ab8
</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.