[v5.15] WARNING in gl861_ctrl_msg/usb_submit_urb

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ef251c45f1cd Linux 5.15.204
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14ad396a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=353ae28c40b35af5
dashboard link: https://syzkaller.appspot.com/bug?extid=7f000fe2ea315f028763
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/bde897c3d01f/disk-ef251c45.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/51b2a5826cd1/vmlinux-ef251c45.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cb95a5a40121/bzImage-ef251c45.xz

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

------------[ cut here ]------------
usb 5-1: BOGUS control dir, pipe 80000280 doesn't match bRequestType c0
WARNING: CPU: 0 PID: 4305 at drivers/usb/core/urb.c:412 usb_submit_urb+0x11a5/0x1910 drivers/usb/core/urb.c:410
Modules linked in:
CPU: 0 PID: 4305 Comm: syz.0.10 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/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 22 c5 8a 48 8b 34 24 4c 89 e2 44 89 f1 e8 ab 83 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:ffffc9000334f508 EFLAGS: 00010246
RAX: 303affea09783a00 RBX: ffff888022a03300 RCX: 0000000000080000
RDX: ffffc9000b9d9000 RSI: 00000000000322c6 RDI: 00000000000322c7
RBP: 1ffff110031ffb86 R08: ffff8880b9033d7f R09: 1ffff110172067af
R10: dffffc0000000000 R11: ffffed10172067b0 R12: ffff888148543960
R13: ffff88807da080f8 R14: 0000000080000280 R15: ffff888018ffdc30
FS: 00007ff528dda6c0(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b32c1cff8 CR3: 00000000731cf000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
usb_start_wait_urb+0x13c/0x580 drivers/usb/core/message.c:61
usb_internal_control_msg drivers/usb/core/message.c:116 [inline]
usb_control_msg+0x231/0x3e0 drivers/usb/core/message.c:166
gl861_ctrl_msg+0x1e9/0x380 drivers/media/usb/dvb-usb-v2/gl861.c:58
gl861_i2c_master_xfer+0x430/0x640 drivers/media/usb/dvb-usb-v2/gl861.c:-1
__i2c_transfer+0x880/0x20b0 drivers/i2c/i2c-core-base.c:-1
i2c_smbus_xfer_emulated drivers/i2c/i2c-core-smbus.c:469 [inline]
__i2c_smbus_xfer+0x1015/0x1dc0 drivers/i2c/i2c-core-smbus.c:607


---
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