[v6.6] WARNING in dib0700_i2c_xfer/usb_submit_urb

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0a805b6ea8cd Linux 6.6.116
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17935012580000
kernel config: https://syzkaller.appspot.com/x/.config?x=12606d4b8832c7e4
dashboard link: https://syzkaller.appspot.com/bug?extid=32addfbe8c14f082797e
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/13874446b4b2/disk-0a805b6e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/69a5e59e1ade/vmlinux-0a805b6e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/322c0711f976/bzImage-0a805b6e.xz

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

------------[ cut here ]------------
usb 1-1: BOGUS control dir, pipe 80000480 doesn't match bRequestType c0
WARNING: CPU: 1 PID: 5976 at drivers/usb/core/urb.c:413 usb_submit_urb+0x10a1/0x17d0 drivers/usb/core/urb.c:411
Modules linked in:
CPU: 1 PID: 5976 Comm: syz.2.19 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:usb_submit_urb+0x10a1/0x17d0 drivers/usb/core/urb.c:411
Code: df 0f b6 44 05 00 84 c0 0f 85 2d 06 00 00 45 0f b6 45 00 48 c7 c7 00 cb 4a 8b 48 8b 74 24 20 4c 89 fa 44 89 f1 e8 cf 51 00 fb <0f> 0b 49 bc 00 00 00 00 00 fc ff df e9 96 f4 ff ff 89 e9 80 e1 07
RSP: 0018:ffffc9000527f870 EFLAGS: 00010246
RAX: dc851f05ecc1b900 RBX: ffff888023303000 RCX: 0000000000080000
RDX: ffffc9000d63b000 RSI: 0000000000007d02 RDI: 0000000000007d03
RBP: 1ffff1100304885a R08: ffffc9000527f567 R09: 1ffff92000a4feac
R10: dffffc0000000000 R11: fffff52000a4fead R12: dffffc0000000000
R13: ffff8880182442d0 R14: 0000000080000480 R15: ffff88802ea66e38
FS: 00007f5d230bf6c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f9ab8f82d58 CR3: 000000007e47b000 CR4: 00000000003506e0
Call Trace:
<TASK>
usb_start_wait_urb+0x115/0x4b0 drivers/usb/core/message.c:59
usb_internal_control_msg drivers/usb/core/message.c:103 [inline]
usb_control_msg+0x233/0x3e0 drivers/usb/core/message.c:154
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+0xb92/0xf60 drivers/media/usb/dvb-usb/dib0700_core.c:361
__i2c_transfer+0x868/0x2080 drivers/i2c/i2c-core-base.c:-1
i2c_transfer+0x250/0x390 drivers/i2c/i2c-core-base.c:2328
i2cdev_ioctl_rdwr+0x3b0/0x690 drivers/i2c/i2c-dev.c:297
i2cdev_ioctl+0x646/0x7e0 drivers/i2c/i2c-dev.c:458
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:871 [inline]
__se_sys_ioctl+0xfd/0x170 fs/ioctl.c:857
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f5d2218efc9
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:00007f5d230bf038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f5d223e5fa0 RCX: 00007f5d2218efc9
RDX: 0000200000000a40 RSI: 0000000000000707 RDI: 0000000000000005
RBP: 00007f5d22211f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f5d223e6038 R14: 00007f5d223e5fa0 R15: 00007ffca870a618
</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: 0a805b6ea8cd Linux 6.6.116
git tree: linux-6.6.y

console output: https://syzkaller.appspot.com/x/log.txt?x=107c3704580000

kernel config: https://syzkaller.appspot.com/x/.config?x=12606d4b8832c7e4
dashboard link: https://syzkaller.appspot.com/bug?extid=32addfbe8c14f082797e
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=147c3704580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=124f132f980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/13874446b4b2/disk-0a805b6e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/69a5e59e1ade/vmlinux-0a805b6e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/322c0711f976/bzImage-0a805b6e.xz

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

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

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

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:usb_submit_urb+0x10a1/0x17d0 drivers/usb/core/urb.c:411
Code: df 0f b6 44 05 00 84 c0 0f 85 2d 06 00 00 45 0f b6 45 00 48 c7 c7 00 cb 4a 8b 48 8b 74 24 20 4c 89 fa 44 89 f1 e8 cf 51 00 fb <0f> 0b 49 bc 00 00 00 00 00 fc ff df e9 96 f4 ff ff 89 e9 80 e1 07

RSP: 0018:ffffc9000482f870 EFLAGS: 00010246
RAX: c7ed73bb9d8d1700 RBX: ffff8880773adc00 RCX: ffff88807b4e5a00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002
RBP: 1ffff110048ab6e6 R08: ffffc9000482f467 R09: 1ffff92000905e8c
R10: dffffc0000000000 R11: fffff52000905e8d R12: dffffc0000000000
R13: ffff88802455b730 R14: 0000000080000280 R15: ffff88802ea0fa50
FS: 0000555592f19500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000

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

CR2: 000055f8c7187018 CR3: 000000007a42b000 CR4: 00000000003506f0

Call Trace:
<TASK>
usb_start_wait_urb+0x115/0x4b0 drivers/usb/core/message.c:59
usb_internal_control_msg drivers/usb/core/message.c:103 [inline]
usb_control_msg+0x233/0x3e0 drivers/usb/core/message.c:154
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+0xb92/0xf60 drivers/media/usb/dvb-usb/dib0700_core.c:361
__i2c_transfer+0x868/0x2080 drivers/i2c/i2c-core-base.c:-1
i2c_transfer+0x250/0x390 drivers/i2c/i2c-core-base.c:2328
i2cdev_ioctl_rdwr+0x3b0/0x690 drivers/i2c/i2c-dev.c:297
i2cdev_ioctl+0x646/0x7e0 drivers/i2c/i2c-dev.c:458
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:871 [inline]
__se_sys_ioctl+0xfd/0x170 fs/ioctl.c:857
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2

RIP: 0033:0x7f85dc98efc9

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:00007fffd5a33068 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f85dcbe5fa0 RCX: 00007f85dc98efc9
RDX: 0000200000000a40 RSI: 0000000000000707 RDI: 0000000000000004
RBP: 00007f85dca11f91 R08: 0000000000000000 R09: 0000000000000000

R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000

R13: 00007f85dcbe5fa0 R14: 00007f85dcbe5fa0 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.