[v5.15] WARNING in bcm5974_start_traffic/usb_submit_urb

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 9465fef4ae35 Linux 5.15.153
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=146a53d3180000
kernel config: https://syzkaller.appspot.com/x/.config?x=74ff83133fa97f6c
dashboard link: https://syzkaller.appspot.com/bug?extid=287375819c124b902cdc
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15f7dda1180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15126f4b180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3c82fda40b43/disk-9465fef4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ec13893dc103/vmlinux-9465fef4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7b44910e5283/Image-9465fef4.gz.xz

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

------------[ cut here ]------------
usb 1-1: BOGUS urb xfer, pipe 1 != type 3
WARNING: CPU: 0 PID: 3978 at drivers/usb/core/urb.c:503 usb_submit_urb+0xa44/0x1588 drivers/usb/core/urb.c:502
Modules linked in:
CPU: 0 PID: 3978 Comm: udevd Not tainted 5.15.153-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : usb_submit_urb+0xa44/0x1588 drivers/usb/core/urb.c:502
lr : usb_submit_urb+0xa44/0x1588 drivers/usb/core/urb.c:502
sp : ffff80001c977370
x29: ffff80001c9773b0 x28: 0000000000000001 x27: ffff800012b4fda8
x26: ffff0000d9286700 x25: ffff0000c21c5000 x24: 0000000000000400
x23: ffff800012b565c0 x22: dfff800000000000 x21: 0000000000000002
x20: 0000000000000cc0 x19: ffff0000c086b000 x18: 0000000000000001
x17: 0000000000000000 x16: ffff80001197d2b4 x15: 00000000ffffffff
x14: ffff0000c9a6b680 x13: 0000000000000001 x12: 0000000000000001
x11: 0000000000000000 x10: 0000000000000000 x9 : 92f6132d1a8ec900
x8 : 92f6132d1a8ec900 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff80001c976ad8 x4 : ffff8000149ef7a0 x3 : ffff80000854e6c0
x2 : 0000000000000001 x1 : 0000000100000000 x0 : 0000000000000029
Call trace:
usb_submit_urb+0xa44/0x1588 drivers/usb/core/urb.c:502
bcm5974_start_traffic+0xe0/0x154 drivers/input/mouse/bcm5974.c:799
bcm5974_open+0x98/0x134 drivers/input/mouse/bcm5974.c:839
input_open_device+0x170/0x29c drivers/input/input.c:640
evdev_open_device drivers/input/evdev.c:400 [inline]
evdev_open+0x308/0x4b4 drivers/input/evdev.c:487
chrdev_open+0x3e8/0x4fc fs/char_dev.c:414
do_dentry_open+0x780/0xed8 fs/open.c:826
vfs_open+0x7c/0x90 fs/open.c:956
do_open fs/namei.c:3608 [inline]
path_openat+0x1f28/0x26f0 fs/namei.c:3742
do_filp_open+0x1a8/0x3b4 fs/namei.c:3769
do_sys_openat2+0x128/0x3d8 fs/open.c:1211
do_sys_open fs/open.c:1227 [inline]
__do_sys_openat fs/open.c:1243 [inline]
__se_sys_openat fs/open.c:1238 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1238
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
irq event stamp: 4354
hardirqs last enabled at (4353): [<ffff80000832abe8>] __up_console_sem+0xb4/0x100 kernel/printk/printk.c:257
hardirqs last disabled at (4354): [<ffff800011978940>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (14): [<ffff8000080310b4>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:31
softirqs last disabled at (12): [<ffff800008031080>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:18
---[ end trace 2e62fe857388afa2 ]---


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

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