[v6.6] WARNING in usb_read/usb_submit_urb

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6282921b6825 Linux 6.6.94
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11c4330c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=96da6b2210cda427
dashboard link: https://syzkaller.appspot.com/bug?extid=64d200d1fec06c9242dc
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/a3bf0d8e22b2/disk-6282921b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d1d442f782d0/vmlinux-6282921b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a8378f4b7e1b/bzImage-6282921b.xz

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

------------[ cut here ]------------
usb 1-1: BOGUS control dir, pipe 80002580 doesn't match bRequestType c1
WARNING: CPU: 1 PID: 15923 at drivers/usb/core/urb.c:413 usb_submit_urb+0x1101/0x1850 drivers/usb/core/urb.c:411
Modules linked in:
CPU: 1 PID: 15923 Comm: syz.3.2704 Not tainted 6.6.94-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:usb_submit_urb+0x1101/0x1850 drivers/usb/core/urb.c:411
Code: df 0f b6 44 05 00 84 c0 0f 85 53 06 00 00 45 0f b6 04 24 48 c7 c7 c0 b3 4a 8b 48 8b 74 24 18 4c 89 fa 44 89 f1 e8 ef 5d 00 fb <0f> 0b 49 bd 00 00 00 00 00 fc ff df e9 37 f4 ff ff 89 e9 80 e1 07
RSP: 0018:ffffc9000f29f848 EFLAGS: 00010246
RAX: 70dbc0dc540f6600 RBX: ffff888030c35400 RCX: 0000000000080000
RDX: ffffc900105b3000 RSI: 00000000000069cb RDI: 00000000000069cc
RBP: 1ffff11028c4bf2c R08: ffffc9000f29f547 R09: 1ffff92001e53ea8
R10: dffffc0000000000 R11: fffff52001e53ea9 R12: ffff88814625f960
R13: dffffc0000000000 R14: 0000000080002580 R15: ffff8880312deca8
FS: 00007fb2c0f256c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c424a3c CR3: 00000000600c7000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
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
usb_read+0xbf/0x120 drivers/i2c/busses/i2c-tiny-usb.c:184
usb_xfer+0x31c/0x710 drivers/i2c/busses/i2c-tiny-usb.c:82
__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:0x7fb2c018e929
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:00007fb2c0f25038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fb2c03b5fa0 RCX: 00007fb2c018e929
RDX: 0000200000000080 RSI: 0000000000000707 RDI: 0000000000000004
RBP: 00007fb2c0210b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fb2c03b5fa0 R15: 00007ffd1b05a5d8
</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: 6282921b6825 Linux 6.6.94
git tree: linux-6.6.y

console output: https://syzkaller.appspot.com/x/log.txt?x=1414cdd4580000

kernel config: https://syzkaller.appspot.com/x/.config?x=96da6b2210cda427
dashboard link: https://syzkaller.appspot.com/bug?extid=64d200d1fec06c9242dc
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=105eb30c580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16b00b0c580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a3bf0d8e22b2/disk-6282921b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d1d442f782d0/vmlinux-6282921b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a8378f4b7e1b/bzImage-6282921b.xz

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

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

usb 4-1: BOGUS control dir, pipe 80000e80 doesn't match bRequestType c1
WARNING: CPU: 0 PID: 5844 at drivers/usb/core/urb.c:413 usb_submit_urb+0x1101/0x1850 drivers/usb/core/urb.c:411
Modules linked in:
CPU: 0 PID: 5844 Comm: syz-executor388 Not tainted 6.6.94-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:usb_submit_urb+0x1101/0x1850 drivers/usb/core/urb.c:411
Code: df 0f b6 44 05 00 84 c0 0f 85 53 06 00 00 45 0f b6 04 24 48 c7 c7 c0 b3 4a 8b 48 8b 74 24 18 4c 89 fa 44 89 f1 e8 ef 5d 00 fb <0f> 0b 49 bd 00 00 00 00 00 fc ff df e9 37 f4 ff ff 89 e9 80 e1 07

RSP: 0018:ffffc9000472f848 EFLAGS: 00010246
RAX: 6e8e6a2b71ca8900 RBX: ffff8880261e1e00 RCX: ffff888024653c00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002
RBP: 1ffff110284ed74a R08: ffffc9000472f447 R09: 1ffff920008e5e88
R10: dffffc0000000000 R11: fffff520008e5e89 R12: ffff88814276ba50
R13: dffffc0000000000 R14: 0000000080000e80 R15: ffff8881462772f8
FS: 0000555561cb2380(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000

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

CR2: 0000555561cb2ca8 CR3: 000000002d47a000 CR4: 00000000003506f0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
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
usb_read+0xbf/0x120 drivers/i2c/busses/i2c-tiny-usb.c:184
usb_xfer+0x31c/0x710 drivers/i2c/busses/i2c-tiny-usb.c:82
__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:0x7ff47e056d59
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 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:00007ffce8ecd5d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000017443 RCX: 00007ff47e056d59

RDX: 0000200000000080 RSI: 0000000000000707 RDI: 0000000000000004

RBP: 0000000000000000 R08: 00232d6332692f76 R09: 0000000000000008
R10: 000000000000001f R11: 0000000000000246 R12: 00007ffce8ecd5fc
R13: 00007ffce8ecd630 R14: 00007ffce8ecd610 R15: 000000000000000c
</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.