Hello,
syzbot found the following issue on:
HEAD commit: 311d8503ef9f Linux 6.1.107
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=12943909980000
kernel config:
https://syzkaller.appspot.com/x/.config?x=44dc66fb9519a1c5
dashboard link:
https://syzkaller.appspot.com/bug?extid=50ec0adcc55ad4d1e33d
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/f3b1a99e840e/disk-311d8503.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/75ff3e2051d3/vmlinux-311d8503.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/c46e3db21279/bzImage-311d8503.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+50ec0a...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 6699 at net/wireless/core.h:231 cfg80211_wext_giwrate net/wireless/wext-compat.c:1325 [inline]
WARNING: CPU: 1 PID: 6699 at net/wireless/core.h:231 __cfg80211_wext_giwrate+0x4a1/0x570 net/wireless/wext-compat.c:1609
Modules linked in:
CPU: 1 PID: 6699 Comm: syz.2.1129 Not tainted 6.1.107-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
RIP: 0010:wdev_lock net/wireless/core.h:231 [inline]
RIP: 0010:cfg80211_wext_giwrate net/wireless/wext-compat.c:1325 [inline]
RIP: 0010:__cfg80211_wext_giwrate+0x4a1/0x570 net/wireless/wext-compat.c:1609
Code: 04 25 28 00 00 00 48 3b 84 24 c0 01 00 00 0f 85 d3 00 00 00 89 d8 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 0f 00 6f f7 <0f> 0b e9 63 fd ff ff e8 03 00 6f f7 0f 0b e9 6d fe ff ff 89 d9 80
RSP: 0018:ffffc90017247a20 EFLAGS: 00010287
RAX: ffffffff8a1bae61 RBX: 0000000000000000 RCX: 0000000000040000
RDX: ffffc9000a081000 RSI: 000000000000039e RDI: 000000000000039f
RBP: ffffc90017247c28 R08: ffffffff8a1bab99 R09: ffffc90017247bb0
R10: ffffffffffffffff R11: dffffc0000000001 R12: 1ffff92002e48f4c
R13: dffffc0000000000 R14: ffff888021b60c90 R15: 1ffff1100436c192
FS: 00007f766f3ff6c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f31beb40000 CR3: 000000004fcaa000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ioctl_standard_call+0xdb/0x280 net/wireless/wext-core.c:1026
wext_ioctl_dispatch+0x16f/0x460 net/wireless/wext-core.c:997
wext_handle_ioctl+0x15b/0x260 net/wireless/wext-core.c:1058
sock_ioctl+0x13b/0x770 net/socket.c:1255
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0xf1/0x160 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f766f579ef9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f766f3ff038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f766f715f80 RCX: 00007f766f579ef9
RDX: 0000000020000040 RSI: 0000000000008b21 RDI: 0000000000000004
RBP: 00007f766f5e793e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f766f715f80 R15: 00007ffec130dee8
</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