[v5.15] WARNING in dtv5100_i2c_xfer/usb_submit_urb

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1c700860e8bc Linux 5.15.185
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17027d70580000
kernel config: https://syzkaller.appspot.com/x/.config?x=db74c56dea20051
dashboard link: https://syzkaller.appspot.com/bug?extid=525f33feb7d61d15e781
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/98c9bcd8fb21/disk-1c700860.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/75eaa3b1c3f3/vmlinux-1c700860.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ed251e9d15fe/bzImage-1c700860.xz

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

------------[ cut here ]------------
usb 5-1: BOGUS control dir, pipe 80000780 doesn't match bRequestType c0
WARNING: CPU: 0 PID: 5237 at drivers/usb/core/urb.c:412 usb_submit_urb+0x1200/0x1980 drivers/usb/core/urb.c:410
Modules linked in:
CPU: 1 PID: 5237 Comm: syz.1.229 Not tainted 5.15.185-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:usb_submit_urb+0x1200/0x1980 drivers/usb/core/urb.c:410
Code: ff df 0f b6 44 05 00 84 c0 0f 85 7d 06 00 00 45 0f b6 07 48 c7 c7 40 62 a4 8a 48 8b 74 24 30 4c 89 e2 44 89 f1 e8 40 8b c7 03 <0f> 0b 49 bd 00 00 00 00 00 fc ff df e9 3b f3 ff ff 89 e9 80 e1 07
RSP: 0018:ffffc9000304f668 EFLAGS: 00010246
RAX: dfbd8273fbd0ce00 RBX: ffff88805e73fa00 RCX: 0000000000080000
RDX: ffffc90003942000 RSI: 0000000000005a6f RDI: 0000000000005a70
RBP: 1ffff1102863bd5e R08: dffffc0000000000 R09: ffffed10172067a8
R10: ffffed10172067a8 R11: 1ffff110172067a7 R12: ffff8880177ee870
R13: dffffc0000000000 R14: 0000000080000780 R15: ffff8881431deaf0
FS: 00007fceb5f426c0(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fdabf59ed87 CR3: 000000005f274000 CR4: 00000000003506f0
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 drivers/media/usb/dvb-usb/dtv5100.c:60 [inline]
dtv5100_i2c_xfer+0x393/0x650 drivers/media/usb/dvb-usb/dtv5100.c:86
__i2c_transfer+0x864/0x2060 drivers/i2c/i2c-core-base.c:-1
i2c_transfer+0x24c/0x390 drivers/i2c/i2c-core-base.c:2330
i2c_transfer_buffer_flags+0x102/0x190 drivers/i2c/i2c-core-base.c:2358
i2c_master_send include/linux/i2c.h:109 [inline]
i2cdev_write+0x87/0x120 drivers/i2c/i2c-dev.c:175
do_loop_readv_writev fs/read_write.c:-1 [inline]
do_iter_write+0x3e4/0x7b0 fs/read_write.c:857
vfs_writev fs/read_write.c:928 [inline]
do_writev+0x254/0x410 fs/read_write.c:971
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:0x7fceb80da929
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:00007fceb5f42038 EFLAGS: 00000246 ORIG_RAX: 0000000000000014
RAX: ffffffffffffffda RBX: 00007fceb8301fa0 RCX: 00007fceb80da929
RDX: 0000000000000001 RSI: 0000200000000500 RDI: 0000000000000008
RBP: 00007fceb815cb39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fceb8301fa0 R15: 00007ffc7cf6e1e8
</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: 1c700860e8bc Linux 5.15.185
git tree: linux-5.15.y

console output: https://syzkaller.appspot.com/x/log.txt?x=14c165d4580000

kernel config: https://syzkaller.appspot.com/x/.config?x=db74c56dea20051
dashboard link: https://syzkaller.appspot.com/bug?extid=525f33feb7d61d15e781
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12c165d4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=144aae82580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/98c9bcd8fb21/disk-1c700860.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/75eaa3b1c3f3/vmlinux-1c700860.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ed251e9d15fe/bzImage-1c700860.xz

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

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

usb 1-1: BOGUS control dir, pipe 80000280 doesn't match bRequestType c0
WARNING: CPU: 1 PID: 4166 at drivers/usb/core/urb.c:412 usb_submit_urb+0x1200/0x1980 drivers/usb/core/urb.c:410
Modules linked in:
CPU: 1 PID: 4166 Comm: syz-executor389 Not tainted 5.15.185-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:usb_submit_urb+0x1200/0x1980 drivers/usb/core/urb.c:410
Code: ff df 0f b6 44 05 00 84 c0 0f 85 7d 06 00 00 45 0f b6 07 48 c7 c7 40 62 a4 8a 48 8b 74 24 30 4c 89 e2 44 89 f1 e8 40 8b c7 03 <0f> 0b 49 bd 00 00 00 00 00 fc ff df e9 3b f3 ff ff 89 e9 80 e1 07

RSP: 0018:ffffc90002edf668 EFLAGS: 00010246
RAX: 5e21497a5e068a00 RBX: ffff88801b589700 RCX: ffff888073d28000
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: 1ffff1100484caa0 R08: dffffc0000000000 R09: ffffed10172267a8
R10: ffffed10172267a8 R11: 1ffff110172267a7 R12: ffff88814883f988
R13: dffffc0000000000 R14: 0000000080000280 R15: ffff888024265500
FS: 000055558ccf6380(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000

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

CR2: 00007f203e8518c8 CR3: 000000007abf3000 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 drivers/media/usb/dvb-usb/dtv5100.c:60 [inline]
dtv5100_i2c_xfer+0x393/0x650 drivers/media/usb/dvb-usb/dtv5100.c:86
__i2c_transfer+0x864/0x2060 drivers/i2c/i2c-core-base.c:-1
i2c_transfer+0x24c/0x390 drivers/i2c/i2c-core-base.c:2330
i2c_transfer_buffer_flags+0x102/0x190 drivers/i2c/i2c-core-base.c:2358
i2c_master_send include/linux/i2c.h:109 [inline]
i2cdev_write+0x87/0x120 drivers/i2c/i2c-dev.c:175
do_loop_readv_writev fs/read_write.c:-1 [inline]
do_iter_write+0x3e4/0x7b0 fs/read_write.c:857
vfs_writev fs/read_write.c:928 [inline]
do_writev+0x254/0x410 fs/read_write.c:971
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:0x7fdddb20a159
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 31 17 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:00007fffcb80b268 EFLAGS: 00000246 ORIG_RAX: 0000000000000014
RAX: ffffffffffffffda RBX: 00007fffcb80b438 RCX: 00007fdddb20a159
RDX: 0000000000000001 RSI: 0000200000000500 RDI: 0000000000000004
RBP: 00007fdddb27d610 R08: 00232d6332692f76 R09: 00007fffcb80b438
R10: 000000000000000f R11: 0000000000000246 R12: 0000000000000001
R13: 00007fffcb80b428 R14: 0000000000000001 R15: 0000000000000001
</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.