[v6.6] WARNING in usb_stor_msg_common/usb_submit_urb

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 5fa4793a2d2d Linux 6.6.119
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1190eb1a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=691a6769a86ac817
dashboard link: https://syzkaller.appspot.com/bug?extid=4812ca3fcc494a040a9d
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=174a4b1a580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/63699875f1dd/disk-5fa4793a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8506652fcb6f/vmlinux-5fa4793a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1b30ceed1710/bzImage-5fa4793a.xz

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

------------[ cut here ]------------
URB ffff88814be0fa00 submitted while active
WARNING: CPU: 0 PID: 5927 at drivers/usb/core/urb.c:379 usb_submit_urb+0xf35/0x17d0 drivers/usb/core/urb.c:379
Modules linked in:
CPU: 0 PID: 5927 Comm: usb-storage Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:usb_submit_urb+0xf35/0x17d0 drivers/usb/core/urb.c:379
Code: 4a 8b 44 89 fa e8 ab 67 10 04 e9 28 fc ff ff e8 61 a6 35 fb c6 05 88 df e4 07 01 48 c7 c7 c0 dc 4a 8b 48 89 de e8 7b 22 00 fb <0f> 0b e9 45 f1 ff ff e8 3f a6 35 fb eb 11 e8 38 a6 35 fb bd 80 00
RSP: 0018:ffffc90003487490 EFLAGS: 00010246
RAX: b9ce0b03c204ba00 RBX: ffff88814be0fa00 RCX: ffff88807a849e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002
RBP: ffffc90003487658 R08: ffffc90003487087 R09: 1ffff92000690e10
R10: dffffc0000000000 R11: fffff52000690e11 R12: dffffc0000000000
R13: ffff888025ed8ed0 R14: ffff88814be0fa08 R15: 0000000000000c00
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000556e51a898e0 CR3: 0000000030074000 CR4: 00000000003506f0
Call Trace:
<TASK>
usb_stor_msg_common+0x27d/0x4b0 drivers/usb/storage/transport.c:143
usb_stor_bulk_transfer_buf+0x151/0x2a0 drivers/usb/storage/transport.c:395
ene_send_scsi_cmd+0x10e/0x5f0 drivers/usb/storage/ene_ub6250.c:502
ene_get_card_type drivers/usb/storage/ene_ub6250.c:1843 [inline]
ene_init+0x14f/0x370 drivers/usb/storage/ene_ub6250.c:2197
ene_transport+0x39ad/0x4650 drivers/usb/storage/ene_ub6250.c:2310
usb_stor_invoke_transport+0xfc/0x1980 drivers/usb/storage/transport.c:611
usb_stor_control_thread+0x447/0x8d0 drivers/usb/storage/usb.c:380
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</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 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