[syzbot] [usb?] WARNING in wdm_rxwork/usb_submit_urb

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:    0468be89b3fa Merge tag 'iommu-updates-v6.6' of git://git.k..
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
console output: https://syzkaller.appspot.com/x/log.txt?x=161a0924680000
kernel config:  https://syzkaller.appspot.com/x/.config?x=89dc1df75beb4d84
dashboard link: https://syzkaller.appspot.com/bug?extid=44a9ac69913e0758fbc1
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1079f65481a7/disk-0468be89.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7eb3c6765fda/vmlinux-0468be89.xz
kernel image: https://storage.googleapis.com/syzbot-assets/92e68aa81913/bzImage-0468be89.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+44a9ac69913e0758fbc1@xxxxxxxxxxxxxxxxxxxxxxxxx

WARNING: CPU: 1 PID: 5266 at drivers/usb/core/urb.c:379 usb_submit_urb+0x14cb/0x1720 drivers/usb/core/urb.c:379
Modules linked in:
CPU: 1 PID: 5266 Comm: kworker/1:4 Not tainted 6.5.0-syzkaller-10885-g0468be89b3fa #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
Workqueue: events wdm_rxwork
RIP: 0010:usb_submit_urb+0x14cb/0x1720 drivers/usb/core/urb.c:379
Code: 27 4b fe eb cb bb fe ff ff ff e9 ca f3 ff ff e8 4b f6 4b fd 48 89 de 48 c7 c7 e0 f1 ee 86 c6 05 45 85 25 05 01 e8 95 af 15 fd <0f> 0b e9 ba fe ff ff bb f8 ff ff ff e9 9e f3 ff ff 48 89 ef e8 6c
RSP: 0018:ffffc90001f57c40 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffff88810efe6b00 RCX: 0000000000000000
RDX: ffff88811e413a00 RSI: ffffffff811725a6 RDI: 0000000000000001
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 205d363632355420 R12: 0000000000000293
R13: ffff8881013c7090 R14: ffff8881013c7050 R15: ffff8881f673acc0
FS:  0000000000000000(0000) GS:ffff8881f6700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f89395c0c98 CR3: 00000001405e6000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 wdm_rxwork+0xf3/0x200 drivers/usb/class/cdc-wdm.c:989
 process_one_work+0x887/0x15d0 kernel/workqueue.c:2630
 process_scheduled_works kernel/workqueue.c:2703 [inline]
 worker_thread+0x8bb/0x1290 kernel/workqueue.c:2784
 kthread+0x33a/0x430 kernel/kthread.c:388
 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304
 </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 syzkaller@xxxxxxxxxxxxxxxx.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup