[v5.15] WARNING in dtv5100_i2c_msg/usb_submit_urb

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3330a8d33e08 Linux 5.15.201
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1769c24a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=353ae28c40b35af5
dashboard link: https://syzkaller.appspot.com/bug?extid=b1e2462b4ca8d357fe18
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b65fe19af112/disk-3330a8d3.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/351948519a0d/vmlinux-3330a8d3.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a3b3f8477595/bzImage-3330a8d3.xz

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

------------[ cut here ]------------
usb 2-1: BOGUS control dir, pipe 80000980 doesn't match bRequestType c0
WARNING: CPU: 1 PID: 5620 at drivers/usb/core/urb.c:412 usb_submit_urb+0x11a5/0x1910 drivers/usb/core/urb.c:410
Modules linked in:
CPU: 1 PID: 5620 Comm: syz.0.283 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
RIP: 0010:usb_submit_urb+0x11a5/0x1910 drivers/usb/core/urb.c:410
Code: fc ff df 0f b6 44 05 00 84 c0 0f 85 6c 06 00 00 45 0f b6 07 48 c7 c7 a0 17 c5 8a 48 8b 34 24 4c 89 e2 44 89 f1 e8 4b 2b d3 03 <0f> 0b 49 bc 00 00 00 00 00 fc ff df e9 92 f3 ff ff 89 e9 80 e1 07
RSP: 0018:ffffc90002eaf808 EFLAGS: 00010246
RAX: 22aa9c8c68869300 RBX: ffff8881483dda00 RCX: 0000000000080000
RDX: ffffc9000c481000 RSI: 0000000000006b61 RDI: 0000000000006b62
RBP: 1ffff1100451076d R08: ffffc90002eaf327 R09: 1ffff920005d5e64
R10: dffffc0000000000 R11: fffff520005d5e65 R12: ffff88802ca90de8
R13: ffff88807f2340f8 R14: 0000000080000980 R15: ffff888022883b68
FS: 00007f88e37456c0(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000020000002e000 CR3: 0000000043c43000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
usb_start_wait_urb+0x128/0x4e0 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+0x231/0x2f0 drivers/media/usb/dvb-usb/dtv5100.c:65
dtv5100_i2c_xfer+0x47c/0x650 drivers/media/usb/dvb-usb/dtv5100.c:86
__i2c_transfer+0x880/0x20b0 drivers/i2c/i2c-core-base.c:-1
i2c_transfer+0x25d/0x3a0 drivers/i2c/i2c-core-base.c:2330
i2cdev_ioctl_rdwr+0x3dc/0x6d0 drivers/i2c/i2c-dev.c:297
i2cdev_ioctl+0x610/0x7b0 drivers/i2c/i2c-dev.c:458
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f88e54eb799
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 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 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f88e3745028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f88e5764fa0 RCX: 00007f88e54eb799
RDX: 00002000000005c0 RSI: 0000000000000707 RDI: 0000000000000005
RBP: 00007f88e5581bd9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f88e5765038 R14: 00007f88e5764fa0 R15: 00007ffcf090edc8
</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: 3330a8d33e08 Linux 5.15.201
git tree: linux-5.15.y

console output: https://syzkaller.appspot.com/x/log.txt?x=1281a8d6580000

kernel config: https://syzkaller.appspot.com/x/.config?x=353ae28c40b35af5
dashboard link: https://syzkaller.appspot.com/bug?extid=b1e2462b4ca8d357fe18
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16b4cd5a580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=167f1b94580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b65fe19af112/disk-3330a8d3.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/351948519a0d/vmlinux-3330a8d3.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a3b3f8477595/bzImage-3330a8d3.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b1e246...@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:412 usb_submit_urb+0x11a5/0x1910 drivers/usb/core/urb.c:410
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 02/12/2026
RIP: 0010:usb_submit_urb+0x11a5/0x1910 drivers/usb/core/urb.c:410
Code: fc ff df 0f b6 44 05 00 84 c0 0f 85 6c 06 00 00 45 0f b6 07 48 c7 c7 a0 17 c5 8a 48 8b 34 24 4c 89 e2 44 89 f1 e8 4b 2b d3 03 <0f> 0b 49 bc 00 00 00 00 00 fc ff df e9 92 f3 ff ff 89 e9 80 e1 07

RSP: 0018:ffffc900031ef808 EFLAGS: 00010246
RAX: 75a8dc1b4ee8af00 RBX: ffff8881445f9a00 RCX: ffff888077599dc0
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: 1ffff1102905046e R08: ffff8880b9133d7f R09: 1ffff110172267af
R10: dffffc0000000000 R11: ffffed10172267b0 R12: ffff8881427bc7a8
R13: ffff88807c6d80f8 R14: 0000000080000280 R15: ffff888148282370
FS: 0000555559662500(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000

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

CR2: 000055d3c478fc50 CR3: 0000000020735000 CR4: 00000000003506f0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
usb_start_wait_urb+0x128/0x4e0 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+0x231/0x2f0 drivers/media/usb/dvb-usb/dtv5100.c:65
dtv5100_i2c_xfer+0x47c/0x650 drivers/media/usb/dvb-usb/dtv5100.c:86
__i2c_transfer+0x880/0x20b0 drivers/i2c/i2c-core-base.c:-1
i2c_transfer+0x25d/0x3a0 drivers/i2c/i2c-core-base.c:2330
i2cdev_ioctl_rdwr+0x3dc/0x6d0 drivers/i2c/i2c-dev.c:297
i2cdev_ioctl+0x610/0x7b0 drivers/i2c/i2c-dev.c:458
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0

RIP: 0033:0x7fdb35d97799

Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 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 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48

RSP: 002b:00007ffe83137d98 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fdb36010fa0 RCX: 00007fdb35d97799
RDX: 00002000000005c0 RSI: 0000000000000707 RDI: 0000000000000004
RBP: 00007fdb35e2dbd9 R08: 0000000000000000 R09: 0000000000000000

R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000

R13: 00007fdb36010fac R14: 00007fdb36010fa0 R15: 00007fdb36010fa0
</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.