[v6.1] WARNING in ADDR_ctrl_msg/usb_submit_urb

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f6e38ae624cf Linux 6.1.158
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11b2e512580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7eb38bd5021fec61
dashboard link: https://syzkaller.appspot.com/bug?extid=1cdb4aa9bf14f8a9230b
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/2b7003e2661d/disk-f6e38ae6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0696cea8d016/vmlinux-f6e38ae6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6b7a89e636d7/bzImage-f6e38ae6.xz

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

usb 2-1: BOGUS control dir, pipe 80000680 doesn't match bRequestType c0
WARNING: CPU: 0 PID: 4882 at drivers/usb/core/urb.c:413 usb_submit_urb+0x11a5/0x1910 drivers/usb/core/urb.c:411
Modules linked in:
CPU: 0 PID: 4882 Comm: syz.1.64 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:usb_submit_urb+0x11a5/0x1910 drivers/usb/core/urb.c:411
Code: ff df 0f b6 44 05 00 84 c0 0f 85 6f 06 00 00 45 0f b6 07 48 c7 c7 80 3a 2e 8b 48 8b 74 24 18 4c 89 e2 44 89 f1 e8 eb 1b 37 fb <0f> 0b 49 bc 00 00 00 00 00 fc ff df e9 93 f3 ff ff 89 e9 80 e1 07
RSP: 0018:ffffc90003807808 EFLAGS: 00010246
RAX: 3efa1b103facd100 RBX: ffff888054b81500 RCX: 0000000000080000
RDX: ffffc9000dc29000 RSI: 000000000002e679 RDI: 000000000002e67a
RBP: 1ffff11003d60345 R08: dffffc0000000000 R09: fffff52000700ea1
R10: fffff52000700ea1 R11: 1ffff92000700ea0 R12: ffff888076984b90
R13: ffff8880799e70f8 R14: 0000000080000680 R15: ffff88801eb01a28
FS: 00007f099b6796c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa4aba37000 CR3: 00000000570ef000 CR4: 00000000003526f0
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
ce6230_ctrl_msg+0x248/0x560 drivers/media/usb/dvb-usb-v2/ce6230.c:61
ce6230_i2c_master_xfer+0x436/0x600 drivers/media/usb/dvb-usb-v2/ce6230.c:113
__i2c_transfer+0x864/0x2260 drivers/i2c/i2c-core-base.c:-1
i2c_transfer+0x24c/0x390 drivers/i2c/i2c-core-base.c:2333
i2cdev_ioctl_rdwr+0x3da/0x6c0 drivers/i2c/i2c-dev.c:297
i2cdev_ioctl+0x5ba/0x750 drivers/i2c/i2c-dev.c:458
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0xfa/0x170 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f099a78f749
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:00007f099b679038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f099a9e5fa0 RCX: 00007f099a78f749
RDX: 0000200000000a40 RSI: 0000000000000707 RDI: 0000000000000005
RBP: 00007f099a813f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f099a9e6038 R14: 00007f099a9e5fa0 R15: 00007ffcc3776588
</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: f6e38ae624cf Linux 6.1.158
git tree: linux-6.1.y

console output: https://syzkaller.appspot.com/x/log.txt?x=16b1d512580000

kernel config: https://syzkaller.appspot.com/x/.config?x=7eb38bd5021fec61
dashboard link: https://syzkaller.appspot.com/bug?extid=1cdb4aa9bf14f8a9230b
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=14c4b8c2580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12c4b8c2580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2b7003e2661d/disk-f6e38ae6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0696cea8d016/vmlinux-f6e38ae6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6b7a89e636d7/bzImage-f6e38ae6.xz

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

------------[ cut here ]------------
usb 1-1: BOGUS control dir, pipe 80000280 doesn't match bRequestType c0
WARNING: CPU: 0 PID: 4424 at drivers/usb/core/urb.c:413 usb_submit_urb+0x11a5/0x1910 drivers/usb/core/urb.c:411
Modules linked in:
CPU: 0 PID: 4424 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+0x11a5/0x1910 drivers/usb/core/urb.c:411
Code: ff df 0f b6 44 05 00 84 c0 0f 85 6f 06 00 00 45 0f b6 07 48 c7 c7 80 3a 2e 8b 48 8b 74 24 18 4c 89 e2 44 89 f1 e8 eb 1b 37 fb <0f> 0b 49 bc 00 00 00 00 00 fc ff df e9 93 f3 ff ff 89 e9 80 e1 07

RSP: 0018:ffffc900034d7808 EFLAGS: 00010246
RAX: db0a9d34afe5f700 RBX: ffff888145772700 RCX: ffff888030850000
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002
RBP: 1ffff110050d3a00 R08: dffffc0000000000 R09: fffff5200069ae91
R10: fffff5200069ae91 R11: 1ffff9200069ae90 R12: ffff888076dcd398
R13: ffff88801e65c0f8 R14: 0000000080000280 R15: ffff88802869d000
FS: 000055558cb27500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000

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

CR2: 000055eb207d1900 CR3: 0000000026619000 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
ce6230_ctrl_msg+0x248/0x560 drivers/media/usb/dvb-usb-v2/ce6230.c:61
ce6230_i2c_master_xfer+0x436/0x600 drivers/media/usb/dvb-usb-v2/ce6230.c:113
__i2c_transfer+0x864/0x2260 drivers/i2c/i2c-core-base.c:-1
i2c_transfer+0x24c/0x390 drivers/i2c/i2c-core-base.c:2333
i2cdev_ioctl_rdwr+0x3da/0x6c0 drivers/i2c/i2c-dev.c:297
i2cdev_ioctl+0x5ba/0x750 drivers/i2c/i2c-dev.c:458
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0xfa/0x170 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2

RIP: 0033:0x7fd49038f749

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:00007ffcda5385c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fd4905e5fa0 RCX: 00007fd49038f749
RDX: 0000200000000a40 RSI: 0000000000000707 RDI: 0000000000000004
RBP: 00007fd490413f91 R08: 0000000000000000 R09: 0000000000000000

R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000

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