[moderation] [usb-storage?] BUG: unable to handle kernel NULL pointer dereference in usb_stor_invoke_transport

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 155a3c003e55 Merge tag 'for-6.16/dm-fixes-2' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10ac67d4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f09d04131ef56b22
dashboard link: https://syzkaller.appspot.com/bug?extid=8740e809b9511fe5a116
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
CC: [gre...@linuxfoundation.org linux-...@vger.kernel.org linu...@vger.kernel.org st...@rowland.harvard.edu usb-s...@lists.one-eyed-alien.net]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9d5286410ac0/disk-155a3c00.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0868b69d53fe/vmlinux-155a3c00.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ac1685a1b894/bzImage-155a3c00.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8740e8...@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 800000006256b067 P4D 800000006256b067 PUD 0
Oops: Oops: 0010 [#1] SMP KASAN PTI
CPU: 0 UID: 0 PID: 11576 Comm: usb-storage Not tainted 6.16.0-rc6-syzkaller-00002-g155a3c003e55 #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:0x0
Code: Unable to access opcode bytes at 0xffffffffffffffd6.
RSP: 0018:ffffc90005427a38 EFLAGS: 00010246
RAX: 1ffff1100dcf59c8 RBX: ffff888021f7a108 RCX: 0000000000000000
RDX: 0000000000000006 RSI: ffffffff8d98544c RDI: ffff88806e7acd48
RBP: ffffc90005427c30 R08: ffffffff8fa0cbf7 R09: 1ffffffff1f4197e
R10: dffffc0000000000 R11: 0000000000000000 R12: 1ffff92000a84f60
R13: ffff88806e7ac070 R14: dffffc0000000000 R15: ffff88806e7acd48
FS: 0000000000000000(0000) GS:ffff888125c4f000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 000000003399e000 CR4: 00000000003526f0
Call Trace:
<TASK>
usb_stor_invoke_transport+0x541/0x19c0 drivers/usb/storage/transport.c:926
usb_stor_control_thread+0x450/0x8e0 drivers/usb/storage/usb.c:462
kthread+0x711/0x8a0 kernel/kthread.c:464
ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148
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:ffffc90005427a38 EFLAGS: 00010246
RAX: 1ffff1100dcf59c8 RBX: ffff888021f7a108 RCX: 0000000000000000
RDX: 0000000000000006 RSI: ffffffff8d98544c RDI: ffff88806e7acd48
RBP: ffffc90005427c30 R08: ffffffff8fa0cbf7 R09: 1ffffffff1f4197e
R10: dffffc0000000000 R11: 0000000000000000 R12: 1ffff92000a84f60
R13: ffff88806e7ac070 R14: dffffc0000000000 R15: ffff88806e7acd48
FS: 0000000000000000(0000) GS:ffff888125c4f000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 000000003399e000 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 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 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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.