Hello,
syzbot found the following issue on:
HEAD commit: 58485ff1a74f Linux 6.1.141
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=1285d682580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=c186557a18643a0b
dashboard link:
https://syzkaller.appspot.com/bug?extid=9bc368710cd5aec03014
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/467cd5b7e60b/disk-58485ff1.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/df87a7313b47/vmlinux-58485ff1.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/597ae3da22ce/bzImage-58485ff1.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+9bc368...@syzkaller.appspotmail.com
------------[ cut here ]------------
usb 1-1: BOGUS control dir, pipe 80000980 doesn't match bRequestType c0
WARNING: CPU: 1 PID: 7919 at drivers/usb/core/urb.c:413 usb_submit_urb+0x11ef/0x1970 drivers/usb/core/urb.c:411
Modules linked in:
CPU: 1 PID: 7919 Comm: syz.4.1062 Not tainted 6.1.141-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:usb_submit_urb+0x11ef/0x1970 drivers/usb/core/urb.c:411
Code: fc ff df 0f b6 44 05 00 84 c0 0f 85 84 06 00 00 45 0f b6 07 48 c7 c7 a0 48 0e 8b 48 8b 34 24 4c 89 e2 44 89 f1 e8 e1 dd 36 fb <0f> 0b 49 bd 00 00 00 00 00 fc ff df e9 46 f3 ff ff 89 e9 80 e1 07
RSP: 0018:ffffc9000e74f870 EFLAGS: 00010246
RAX: 7555d354611e7200 RBX: ffff888028647200 RCX: 0000000000080000
RDX: ffffc9000dfca000 RSI: 00000000000052ee RDI: 00000000000052ef
RBP: 1ffff1100aa9cfdb R08: dffffc0000000000 R09: fffff52001ce9e9d
R10: fffff52001ce9e9d R11: 1ffff92001ce9e9c R12: ffff888030b26ac8
R13: dffffc0000000000 R14: 0000000080000980 R15: ffff8880554e7ed8
FS: 00007f9ae3aa26c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f6eb9240000 CR3: 000000006883a000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
usb_start_wait_urb+0x111/0x4b0 drivers/usb/core/message.c:58
usb_internal_control_msg drivers/usb/core/message.c:102 [inline]
usb_control_msg+0x22f/0x3e0 drivers/usb/core/message.c:153
dib0700_ctrl_rd drivers/media/usb/dvb-usb/dib0700_core.c:95 [inline]
dib0700_i2c_xfer_legacy drivers/media/usb/dvb-usb/dib0700_core.c:315 [inline]
dib0700_i2c_xfer+0xbbd/0xf80 drivers/media/usb/dvb-usb/dib0700_core.c:361
__i2c_transfer+0x864/0x2260 drivers/i2c/i2c-core-base.c:-1
i2c_transfer+0x24c/0x390 drivers/i2c/i2c-core-base.c:2333
i2cdev_ioctl_rdwr+0x3da/0x6c0 drivers/i2c/i2c-dev.c:297
i2cdev_ioctl+0x5ba/0x750 drivers/i2c/i2c-dev.c:458
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0xfa/0x170 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f9ae2b8e929
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:00007f9ae3aa2038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f9ae2db5fa0 RCX: 00007f9ae2b8e929
RDX: 0000200000002580 RSI: 0000000000000707 RDI: 0000000000000004
RBP: 00007f9ae2c10b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f9ae2db5fa0 R15: 00007ffff9e238a8
</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