From: syzbot <syzbot+50c258b43e6a020d124f@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, stern@rowland.harvard.edu,
syzkaller-bugs@googlegroups.com,
usb-storage@lists.one-eyed-alien.net
Subject: [syzbot] [usb-storage?] WARNING in usb_stor_scan_dwork/usb_submit_urb
Date: Mon, 24 Aug 2026 22:13:28 -0700 [thread overview]
Message-ID: <6a8d2478.a5a502ce.31d34.001f.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: e1e6e541c5c9 Merge tag 'thunderbolt-for-v7.3-rc1' of ssh:/..
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=168c0179580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8bdeea7ee6735f91
dashboard link: https://syzkaller.appspot.com/bug?extid=50c258b43e6a020d124f
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3b0a1f8e6a1f/disk-e1e6e541.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f98d855e85e8/vmlinux-e1e6e541.xz
kernel image: https://storage.googleapis.com/syzbot-assets/db2c3a41df6d/bzImage-e1e6e541.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+50c258b43e6a020d124f@syzkaller.appspotmail.com
------------[ cut here ]------------
URB ffff888103ab5d00 submitted while active
WARNING: drivers/usb/core/urb.c:379 at usb_submit_urb+0x1689/0x19b0 drivers/usb/core/urb.c:379, CPU#0: kworker/0:4/5231
Modules linked in:
CPU: 0 UID: 0 PID: 5231 Comm: kworker/0:4 Not tainted syzkaller #0 PREEMPT(lazy)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Workqueue: events_freezable usb_stor_scan_dwork
RIP: 0010:usb_submit_urb+0x168c/0x19b0 drivers/usb/core/urb.c:379
Code: 00 48 8b 04 24 48 8b 90 b0 00 00 00 e9 70 ff ff ff bb ed ff ff ff e9 ac f1 ff ff e8 ce 9a ba fc 48 8d 3d 67 f4 00 06 48 89 de <67> 48 0f b9 3a bb f0 ff ff ff e9 8e f1 ff ff c7 44 24 30 00 00 00
RSP: 0018:ffffc90002dafa48 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff888103ab5d00 RCX: dffffc0000000000
RDX: ffff888119261e00 RSI: ffff888103ab5d00 RDI: ffffffff8afa6e20
RBP: 1ffff920005b5f5c R08: 0000000000000002 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff88813cc60fb0
R13: ffff88813cc60f28 R14: ffffc90002dafb00 R15: ffff888103ab5d00
FS: 0000000000000000(0000) GS:ffff888268633000(0000) knlGS:0000000000000000
Call Trace:
<TASK>
usb_stor_scan_dwork+0x1e6/0x2c0 drivers/usb/storage/usb.c:988
process_one_work+0xa23/0x1940 kernel/workqueue.c:3322
process_scheduled_works kernel/workqueue.c:3405 [inline]
worker_thread+0x5ef/0xe50 kernel/workqueue.c:3486
kthread+0x370/0x450 kernel/kthread.c:436
ret_from_fork+0x69a/0xc80 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
----------------
Code disassembly (best guess):
0: 00 48 8b add %cl,-0x75(%rax)
3: 04 24 add $0x24,%al
5: 48 8b 90 b0 00 00 00 mov 0xb0(%rax),%rdx
c: e9 70 ff ff ff jmp 0xffffff81
11: bb ed ff ff ff mov $0xffffffed,%ebx
16: e9 ac f1 ff ff jmp 0xfffff1c7
1b: e8 ce 9a ba fc call 0xfcba9aee
20: 48 8d 3d 67 f4 00 06 lea 0x600f467(%rip),%rdi # 0x600f48e
27: 48 89 de mov %rbx,%rsi
* 2a: 67 48 0f b9 3a ud1 (%edx),%rdi <-- trapping instruction
2f: bb f0 ff ff ff mov $0xfffffff0,%ebx
34: e9 8e f1 ff ff jmp 0xfffff1c7
39: c7 .byte 0xc7
3a: 44 24 30 rex.R and $0x30,%al
3d: 00 00 add %al,(%rax)
---
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@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
reply other threads:[~2026-08-25 5:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6a8d2478.a5a502ce.31d34.001f.GAE@google.com \
--to=syzbot+50c258b43e6a020d124f@syzkaller.appspotmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=syzkaller-bugs@googlegroups.com \
--cc=usb-storage@lists.one-eyed-alien.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox