[v6.6] WARNING in gl861_ctrl_msg/usb_submit_urb

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: cbb31f77b879 Linux 6.6.121
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13f66452580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2a950bf7c0bff9f9
dashboard link: https://syzkaller.appspot.com/bug?extid=0fb22d8d1996d2661445
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/6436cbae3604/disk-cbb31f77.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8f3a3d318f99/vmlinux-cbb31f77.xz
kernel image: https://storage.googleapis.com/syzbot-assets/84920a2a012f/bzImage-cbb31f77.xz

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

------------[ cut here ]------------
usb 3-1: BOGUS control dir, pipe 80000480 doesn't match bRequestType c0
WARNING: CPU: 1 PID: 6418 at drivers/usb/core/urb.c:413 usb_submit_urb+0x10ac/0x17d0 drivers/usb/core/urb.c:411
Modules linked in:
CPU: 1 PID: 6418 Comm: syz.1.219 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:usb_submit_urb+0x10ac/0x17d0 drivers/usb/core/urb.c:411
Code: df 0f b6 44 05 00 84 c0 0f 85 29 06 00 00 45 0f b6 45 00 48 c7 c7 20 35 6b 8b 48 8b 74 24 20 4c 89 fa 44 89 f1 e8 84 b7 ef fa <0f> 0b 49 bc 00 00 00 00 00 fc ff df e9 96 f4 ff ff 89 e9 80 e1 07
RSP: 0018:ffffc9000d04f7d0 EFLAGS: 00010246
RAX: 07d6c4f236d8c100 RBX: ffff88802628c200 RCX: 0000000000080000
RDX: ffffc9000ddbc000 RSI: 0000000000005a40 RDI: 0000000000005a41
RBP: 1ffff1102864c1c7 R08: ffffc9000d04f3c7 R09: 1ffff92001a09e78
R10: dffffc0000000000 R11: fffff52001a09e79 R12: dffffc0000000000
R13: ffff888143260e38 R14: 0000000080000480 R15: ffff888018e929d8
FS: 00007fb50d5f66c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3b7dbb1e9c CR3: 000000002eabd000 CR4: 00000000003506e0
Call Trace:
<TASK>
usb_start_wait_urb+0x12c/0x4e0 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
gl861_ctrl_msg+0x215/0x3d0 drivers/media/usb/dvb-usb-v2/gl861.c:58
gl861_i2c_master_xfer+0x434/0x640 drivers/media/usb/dvb-usb-v2/gl861.c:-1
__i2c_transfer+0x884/0x20c0 drivers/i2c/i2c-core-base.c:-1
i2c_transfer+0x261/0x3a0 drivers/i2c/i2c-core-base.c:2328
i2cdev_ioctl_rdwr+0x3b0/0x690 drivers/i2c/i2c-dev.c:297
i2cdev_ioctl+0x6a0/0x840 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:46 [inline]
do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fb50f39aeb9
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:00007fb50d5f6028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fb50f615fa0 RCX: 00007fb50f39aeb9
RDX: 0000200000000200 RSI: 0000000000000707 RDI: 0000000000000004
RBP: 00007fb50f408c1f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fb50f616038 R14: 00007fb50f615fa0 R15: 00007ffcaaac0278
</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