WARNING in ieee80211_probe_client

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 2c746135 Linux 4.19.158
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=149e1125500000
kernel config: https://syzkaller.appspot.com/x/.config?x=c19abec6250dfe36
dashboard link: https://syzkaller.appspot.com/bug?extid=475bbdf454720ae929d0
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16200a9e500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=156d8b25500000

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

wlan1: Created IBSS using preconfigured BSSID 50:50:50:50:50:50
wlan1: Creating new IBSS network, BSSID 50:50:50:50:50:50
IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
------------[ cut here ]------------
WARNING: CPU: 0 PID: 8133 at net/mac80211/cfg.c:3417 ieee80211_probe_client.cold+0x11/0x2c net/mac80211/cfg.c:3417
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 8133 Comm: syz-executor502 Not tainted 4.19.158-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2fe lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x61 kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:ieee80211_probe_client.cold+0x11/0x2c net/mac80211/cfg.c:3417
Code: 8d 60 01 4c 89 a3 88 17 00 00 e9 3e e8 ff ff 48 89 ef e8 8e be dc f9 eb df e8 27 97 a6 f9 48 c7 c7 c0 12 67 89 e8 aa 90 91 f9 <0f> 0b 41 bc ea ff ff ff e9 32 ef ff ff 90 90 90 90 90 90 90 90 90
RSP: 0018:ffff8880b066f5b0 EFLAGS: 00010286
RAX: 0000000000000024 RBX: ffff888098059100 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814fdba1 RDI: ffffed10160cdea8
RBP: ffff8880a4b9fd60 R08: 0000000000000024 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff8880a25a10a0
R13: 0000000000000000 R14: 0000000000000001 R15: ffffffff89671e80
rdev_probe_client net/wireless/rdev-ops.h:909 [inline]
nl80211_probe_client+0x39e/0xc30 net/wireless/nl80211.c:11600
genl_family_rcv_msg+0x642/0xc40 net/netlink/genetlink.c:602
genl_rcv_msg+0xbf/0x160 net/netlink/genetlink.c:627
netlink_rcv_skb+0x160/0x440 net/netlink/af_netlink.c:2455
genl_rcv+0x24/0x40 net/netlink/genetlink.c:638
netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]
netlink_unicast+0x4d5/0x690 net/netlink/af_netlink.c:1344
netlink_sendmsg+0x6bb/0xc40 net/netlink/af_netlink.c:1909
sock_sendmsg_nosec net/socket.c:622 [inline]
sock_sendmsg+0xc3/0x120 net/socket.c:632
___sys_sendmsg+0x7bb/0x8e0 net/socket.c:2115
__sys_sendmsg net/socket.c:2153 [inline]
__do_sys_sendmsg net/socket.c:2162 [inline]
__se_sys_sendmsg net/socket.c:2160 [inline]
__x64_sys_sendmsg+0x132/0x220 net/socket.c:2160
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x441939
Code: e8 dc 05 03 00 48 83 c4 18 c3 0f 1f 80 00 00 00 00 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 0f 83 8b 0d fc ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fff3d696918 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 0000000000441939
RDX: 0000000000000000 RSI: 0000000020000200 RDI: 0000000000000005
RBP: 000000306e616c77 R08: 0000001d00000000 R09: 0000001d00000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000032
R13: 0000000000000000 R14: 000000000000000c R15: 0000000000000004
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches