[syzbot] [usb-storage?] BUG: unable to handle kernel NULL pointer dereference in usb_stor_invoke_transport (2)

Hello,

syzbot found the following issue on:

HEAD commit:    28924df2a08f Merge tag 'perf-tools-fixes-for-v7.3-2026-09-..
git tree:       upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=16145749580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=5e4e3a0e188a497e
dashboard link: https://syzkaller.appspot.com/bug?extid=356ae236154297f0d60d
compiler:       Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=14bf2a15580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=15023b9e580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/dbb658780e3f/disk-28924df2.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ed954d86e83d/vmlinux-28924df2.xz
kernel image: https://storage.googleapis.com/syzbot-assets/56cc5fdb5ce4/bzImage-28924df2.xz

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

BUG: kernel NULL pointer dereference, address: 0000000000000000
#PF: supervisor instruction fetch in kernel mode
#PF: error_code(0x0010) - not-present page
PGD 80000000733dc067 P4D 80000000733dc067 PUD 7324b067 PMD 0 
Oops: Oops: 0010 [#1] SMP KASAN PTI
CPU: 0 UID: 0 PID: 5644 Comm: usb-storage Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:0x0
Code: Unable to access opcode bytes at 0xffffffffffffffd6.
RSP: 0018:ffffc90003997af8 EFLAGS: 00010246
RAX: 1ffff1100f2c69f0 RBX: ffff888073cbd110 RCX: ffffffff9a9de501
RDX: 0000000000000001 RSI: ffffffff8e474d50 RDI: ffff888079634e90
RBP: ffffc90003997cd0 R08: ffffffff907a1e7f R09: 1ffffffff20f43cf
R10: dffffc0000000000 R11: 0000000000000000 R12: 1ffff1100f2c680e
R13: 1ffff92000732f74 R14: ffff888079634e90 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff888124cd6000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 00000000729a6000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 usb_stor_invoke_transport+0x55a/0x1a40 drivers/usb/storage/transport.c:926
 usb_stor_control_thread+0x44c/0x8f0 drivers/usb/storage/usb.c:462
 kthread+0x38b/0x480 kernel/kthread.c:436
 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
Modules linked in:
CR2: 0000000000000000
---[ end trace 0000000000000000 ]---
RIP: 0010:0x0
Code: Unable to access opcode bytes at 0xffffffffffffffd6.
RSP: 0018:ffffc90003997af8 EFLAGS: 00010246
RAX: 1ffff1100f2c69f0 RBX: ffff888073cbd110 RCX: ffffffff9a9de501
RDX: 0000000000000001 RSI: ffffffff8e474d50 RDI: ffff888079634e90
RBP: ffffc90003997cd0 R08: ffffffff907a1e7f R09: 1ffffffff20f43cf
R10: dffffc0000000000 R11: 0000000000000000 R12: 1ffff1100f2c680e
R13: 1ffff92000732f74 R14: ffff888079634e90 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff888124cd6000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 00000000729a6000 CR4: 00000000003526f0


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