[v6.1] WARNING in dtv5100_i2c_msg/usb_submit_urb

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7b34dc04e4ff Linux 6.1.154
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12af912f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=7eb38bd5021fec61
dashboard link: https://syzkaller.appspot.com/bug?extid=b04e1cf3a4c05ba313be
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1f1ed5df43e0/disk-7b34dc04.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/941b7c0f58be/vmlinux-7b34dc04.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6fb9bad299e4/bzImage-7b34dc04.xz

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

------------[ cut here ]------------
usb 1-1: BOGUS control dir, pipe 80000380 doesn't match bRequestType c0
WARNING: CPU: 1 PID: 4897 at drivers/usb/core/urb.c:413 usb_submit_urb+0x11a5/0x1910 drivers/usb/core/urb.c:411
Modules linked in:
CPU: 1 PID: 4897 Comm: syz.0.142 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
RIP: 0010:usb_submit_urb+0x11a5/0x1910 drivers/usb/core/urb.c:411
Code: ff df 0f b6 44 05 00 84 c0 0f 85 6f 06 00 00 45 0f b6 07 48 c7 c7 60 3f 2e 8b 48 8b 74 24 18 4c 89 e2 44 89 f1 e8 fb 4d 37 fb <0f> 0b 49 bc 00 00 00 00 00 fc ff df e9 93 f3 ff ff 89 e9 80 e1 07
RSP: 0018:ffffc90003c47588 EFLAGS: 00010246
RAX: 154efab3b777f300 RBX: ffff88806222f100 RCX: 0000000000080000
RDX: ffffc9000dbc9000 RSI: 00000000000081ad RDI: 00000000000081ae
RBP: 1ffff1100af9679a R08: dffffc0000000000 R09: fffff52000788e41
R10: fffff52000788e41 R11: 1ffff92000788e40 R12: ffff88801ba50fa0
R13: ffff8880586ca0f8 R14: 0000000080000380 R15: ffff888057cb3cd0
FS: 00007f466262b6c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f466260ad58 CR3: 0000000057b18000 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
dtv5100_i2c_msg+0x22a/0x2d0 drivers/media/usb/dvb-usb/dtv5100.c:60
dtv5100_i2c_xfer+0x1a0/0x3b0 drivers/media/usb/dvb-usb/dtv5100.c:86
__i2c_transfer+0x864/0x2260 drivers/i2c/i2c-core-base.c:-1
i2c_smbus_xfer_emulated drivers/i2c/i2c-core-smbus.c:469 [inline]
__i2c_smbus_xfer+0x1007/0x1fc0 drivers/i2c/i2c-core-smbus.c:607
i2c_smbus_xfer+0x263/0x3a0 drivers/i2c/i2c-core-smbus.c:545
i2cdev_ioctl_smbus+0x1af/0x650 drivers/i2c/i2c-dev.c:348
i2cdev_ioctl+0x545/0x750 drivers/i2c/i2c-dev.c:467
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:0x7f466178eec9
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:00007f466262b038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f46619e5fa0 RCX: 00007f466178eec9
RDX: 00002000000001c0 RSI: 0000000000000720 RDI: 0000000000000006
RBP: 00007f4661811f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f46619e6038 R14: 00007f46619e5fa0 R15: 00007fffd5955e78
</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]

syzbot has found a reproducer for the following issue on:

HEAD commit: 882efbdd9d34 Linux 6.1.155
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12e965cd980000

kernel config: https://syzkaller.appspot.com/x/.config?x=7eb38bd5021fec61
dashboard link: https://syzkaller.appspot.com/bug?extid=b04e1cf3a4c05ba313be
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=126e9334580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=167bc92f980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/23ee6a61dc15/disk-882efbdd.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0bb5f10b3f6e/vmlinux-882efbdd.xz
kernel image: https://storage.googleapis.com/syzbot-assets/64776e288bcc/bzImage-882efbdd.xz

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

------------[ cut here ]------------

usb 1-1: BOGUS control dir, pipe 80000280 doesn't match bRequestType c0
WARNING: CPU: 1 PID: 4432 at drivers/usb/core/urb.c:413 usb_submit_urb+0x11a5/0x1910 drivers/usb/core/urb.c:411
Modules linked in:
CPU: 1 PID: 4432 Comm: syz.0.17 Not tainted syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
RIP: 0010:usb_submit_urb+0x11a5/0x1910 drivers/usb/core/urb.c:411

Code: ff df 0f b6 44 05 00 84 c0 0f 85 6f 06 00 00 45 0f b6 07 48 c7 c7 60 3f 2e 8b 48 8b 74 24 18 4c 89 e2 44 89 f1 e8 9b 41 37 fb <0f> 0b 49 bc 00 00 00 00 00 fc ff df e9 93 f3 ff ff 89 e9 80 e1 07
RSP: 0018:ffffc900034e7848 EFLAGS: 00010246
RAX: 98b74e1fe3b69900 RBX: ffff888018432b00 RCX: ffff888026af1dc0
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002
RBP: 1ffff11003a7c8f0 R08: dffffc0000000000 R09: fffff5200069cea9
R10: fffff5200069cea9 R11: 1ffff9200069cea8 R12: ffff8880290b6d70
R13: ffff88807bc8b0f8 R14: 0000000080000280 R15: ffff88801d3e4780
FS: 000055558c1c3500(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 0000001b2d963fff CR3: 00000000787fa000 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
dtv5100_i2c_msg+0x22a/0x2d0 drivers/media/usb/dvb-usb/dtv5100.c:60
dtv5100_i2c_xfer+0x1a0/0x3b0 drivers/media/usb/dvb-usb/dtv5100.c:86
__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:0x7f7da8d8eec9

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:00007fff28108fa8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f7da8fe5fa0 RCX: 00007f7da8d8eec9
RDX: 0000200000000280 RSI: 0000000000000707 RDI: 0000000000000004
RBP: 00007f7da8e11f91 R08: 0000000000000000 R09: 0000000000000000

R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000

R13: 00007f7da8fe5fa0 R14: 00007f7da8fe5fa0 R15: 0000000000000003
</TASK>


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.