Hello,
syzbot found the following issue on:
HEAD commit: 42616e0f09fb Linux 6.1.15
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=11be33d4c80000
kernel config:
https://syzkaller.appspot.com/x/.config?x=690b9ff41783cd73
dashboard link:
https://syzkaller.appspot.com/bug?extid=7ea49a55c23a17207480
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/db869f2ed2bd/disk-42616e0f.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/37951bbe5829/vmlinux-42616e0f.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/23aa1a75ce0f/bzImage-42616e0f.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+7ea49a...@syzkaller.appspotmail.com
------------[ cut here ]------------
wlan0: Failed check-sdata-in-driver check, flags: 0x0
WARNING: CPU: 0 PID: 9851 at net/mac80211/main.c:287 ieee80211_link_info_change_notify+0x1b2/0x220 net/mac80211/main.c:287
Modules linked in:
CPU: 0 PID: 9851 Comm: syz-executor.1 Not tainted 6.1.15-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:ieee80211_link_info_change_notify+0x1b2/0x220 net/mac80211/main.c:287
Code: b4 99 e7 f7 49 8b 86 08 09 00 00 49 81 c6 28 09 00 00 48 85 c0 4c 0f 45 f0 48 c7 c7 00 8e fb 8b 4c 89 f6 89 ea e8 ee f0 59 f7 <0f> 0b e9 3a ff ff ff 89 e9 80 e1 07 80 c1 03 38 c1 0f 8c c9 fe ff
RSP: 0018:ffffc9000a60f3c8 EFLAGS: 00010246
RAX: b7b1f22e92178e00 RBX: 0000000002000000 RCX: 0000000000040000
RDX: ffffc9000bdf9000 RSI: 0000000000004b89 RDI: 0000000000004b8a
RBP: 0000000000000000 R08: ffffffff816dec4c R09: fffff520014c1e31
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88807a640de0
R13: dffffc0000000000 R14: ffff8880271b4000 R15: ffff8880271b6248
FS: 00007f76c07f0700(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff4cdb821b8 CR3: 000000001bd4a000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ieee80211_set_mcast_rate+0x42/0x50 net/mac80211/cfg.c:2835
rdev_set_mcast_rate net/wireless/rdev-ops.h:1220 [inline]
nl80211_set_mcast_rate+0xb58/0xf90 net/wireless/nl80211.c:11305
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:2550
genl_rcv+0x24/0x40 net/netlink/genetlink.c:861
netlink_unicast_kernel net/netlink/af_netlink.c:1328 [inline]
netlink_unicast+0x7bf/0x990 net/netlink/af_netlink.c:1354
netlink_sendmsg+0x9fe/0xd10 net/netlink/af_netlink.c:1931
sock_sendmsg_nosec net/socket.c:714 [inline]
sock_sendmsg net/socket.c:734 [inline]
____sys_sendmsg+0x59e/0x8f0 net/socket.c:2485
___sys_sendmsg net/socket.c:2539 [inline]
__sys_sendmsg+0x2a9/0x390 net/socket.c:2568
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:0x7f76bfa8c0f9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f76c07f0168 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007f76bfbabf80 RCX: 00007f76bfa8c0f9
RDX: 0000000000000000 RSI: 0000000020000cc0 RDI: 0000000000000003
RBP: 00007f76bfae7ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fffdf745cff R14: 00007f76c07f0300 R15: 0000000000022000
</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.