[moderation] [usb?] general protection fault in vhci_tx_loop

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: fd0584d220fe Merge tag 'trace-tools-v6.13-rc4' of git://gi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1532d2c4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4c4096b0d467a682
dashboard link: https://syzkaller.appspot.com/bug?extid=cfa3bdfa49441f650b85
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [gre...@linuxfoundation.org i...@zenithal.me linux-...@vger.kernel.org linu...@vger.kernel.org sh...@kernel.org valentin...@gmail.com]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/74af16980104/disk-fd0584d2.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c64c22719556/vmlinux-fd0584d2.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e1db2ccf2b68/bzImage-fd0584d2.xz

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

Oops: general protection fault, probably for non-canonical address 0xdffffc0000000003: 0000 [#1] PREEMPT SMP KASAN PTI
KASAN: null-ptr-deref in range [0x0000000000000018-0x000000000000001f]
CPU: 0 UID: 0 PID: 7800 Comm: vhci_tx Not tainted 6.13.0-rc4-syzkaller-00071-gfd0584d220fe #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:setup_cmd_submit_pdu drivers/usb/usbip/vhci_tx.c:16 [inline]
RIP: 0010:vhci_send_cmd_submit drivers/usb/usbip/vhci_tx.c:95 [inline]
RIP: 0010:vhci_tx_loop+0x59e/0x1d10 drivers/usb/usbip/vhci_tx.c:241
Code: f9 49 8d 5c 24 08 48 89 d8 48 c1 e8 03 42 80 3c 28 00 74 08 48 89 df e8 e0 6a 51 fa 4c 8b 3b 49 8d 5f 18 48 89 d8 48 c1 e8 03 <42> 80 3c 28 00 74 08 48 89 df e8 c3 6a 51 fa 4c 8b 2b 48 b8 00 00
RSP: 0018:ffffc9000c7a7ae0 EFLAGS: 00010206
RAX: 0000000000000003 RBX: 0000000000000018 RCX: ffff888027f45a00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc9000c7a7ed0 R08: ffffffff87b1e578 R09: 00000000ffffffff
R10: dffffc0000000000 R11: fffffbfff2030a4f R12: ffff8880610cc100
R13: dffffc0000000000 R14: ffff8880207d37a0 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffef93a6040 CR3: 0000000028b62000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 000000000000000e DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
kthread+0x2f0/0x390 kernel/kthread.c:389
ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:setup_cmd_submit_pdu drivers/usb/usbip/vhci_tx.c:16 [inline]
RIP: 0010:vhci_send_cmd_submit drivers/usb/usbip/vhci_tx.c:95 [inline]
RIP: 0010:vhci_tx_loop+0x59e/0x1d10 drivers/usb/usbip/vhci_tx.c:241
Code: f9 49 8d 5c 24 08 48 89 d8 48 c1 e8 03 42 80 3c 28 00 74 08 48 89 df e8 e0 6a 51 fa 4c 8b 3b 49 8d 5f 18 48 89 d8 48 c1 e8 03 <42> 80 3c 28 00 74 08 48 89 df e8 c3 6a 51 fa 4c 8b 2b 48 b8 00 00
RSP: 0018:ffffc9000c7a7ae0 EFLAGS: 00010206
RAX: 0000000000000003 RBX: 0000000000000018 RCX: ffff888027f45a00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc9000c7a7ed0 R08: ffffffff87b1e578 R09: 00000000ffffffff
R10: dffffc0000000000 R11: fffffbfff2030a4f R12: ffff8880610cc100
R13: dffffc0000000000 R14: ffff8880207d37a0 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055667e6b3018 CR3: 000000003007e000 CR4: 00000000003526f0
----------------
Code disassembly (best guess):
0: f9 stc
1: 49 8d 5c 24 08 lea 0x8(%r12),%rbx
6: 48 89 d8 mov %rbx,%rax
9: 48 c1 e8 03 shr $0x3,%rax
d: 42 80 3c 28 00 cmpb $0x0,(%rax,%r13,1)
12: 74 08 je 0x1c
14: 48 89 df mov %rbx,%rdi
17: e8 e0 6a 51 fa call 0xfa516afc
1c: 4c 8b 3b mov (%rbx),%r15
1f: 49 8d 5f 18 lea 0x18(%r15),%rbx
23: 48 89 d8 mov %rbx,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 80 3c 28 00 cmpb $0x0,(%rax,%r13,1) <-- trapping instruction
2f: 74 08 je 0x39
31: 48 89 df mov %rbx,%rdi
34: e8 c3 6a 51 fa call 0xfa516afc
39: 4c 8b 2b mov (%rbx),%r13
3c: 48 rex.W
3d: b8 .byte 0xb8


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