[syzbot] [usb?] general protection fault in wcove_typec_probe
syzbot <[email protected]>
| Newsgroups | org.kernel.vger.linux-kernel,org.kernel.vger.linux-usb |
|---|---|
| Message-ID | <[email protected]> |
Hello, syzbot found the following issue on: HEAD commit: 8d3ae59288f1 Linux 7.2 git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=14ea0679580000 kernel config: https://syzkaller.appspot.com/x/.config?x=a0fdc3b566746377 dashboard link: https://syzkaller.appspot.com/bug?extid=1a01783ea233350598b5 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/571b2fa98290/disk-8d3ae592.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/5758aecc42aa/vmlinux-8d3ae592.xz kernel image: https://storage.googleapis.com/syzbot-assets/f9306cccc3b8/bzImage-8d3ae592.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: [email protected] Oops: general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f] CPU: 0 UID: 0 PID: 6187 Comm: syz.5.107 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/2026 RIP: 0010:wcove_typec_probe+0xdb/0x780 drivers/usb/typec/tcpm/wcove.c:621 Code: 48 c1 ea 03 80 3c 02 00 0f 85 af 05 00 00 48 8d 7d 08 4d 89 af 88 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 7f 05 00 00 49 8d bf 90 00 00 00 48 8b 6d 08 48 RSP: 0018:ffffc9000594fb18 EFLAGS: 00010212 RAX: dffffc0000000000 RBX: ffff88801e371000 RCX: 0000000000000000 RDX: 0000000000000001 RSI: 0000000000000001 RDI: 0000000000000008 RBP: 0000000000000000 R08: 0000000000000004 R09: 0000000000000000 R10: ffff888035b4d483 R11: 0000000000000000 R12: ffffffff90281e28 R13: ffff88801e371010 R14: ffff888035b4d4c0 R15: ffff888035b4d438 FS: 00007f3b03bde6c0(0000) GS:ffff888123de1000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000110c3be387 CR3: 0000000013036000 CR4: 0000000000350ef0 Call Trace: <TASK> platform_probe+0x106/0x1d0 drivers/base/platform.c:1439 call_driver_probe drivers/base/dd.c:628 [inline] really_probe+0x241/0xa60 drivers/base/dd.c:706 __driver_probe_device+0x20e/0x450 drivers/base/dd.c:868 device_driver_attach+0xd1/0x220 drivers/base/dd.c:1203 bind_store+0xf4/0x190 drivers/base/bus.c:267 drv_attr_store+0x74/0xb0 drivers/base/bus.c:125 sysfs_kf_write+0xf2/0x150 fs/sysfs/file.c:145 kernfs_fop_write_iter+0x3e0/0x5f0 fs/kernfs/file.c:345 new_sync_write fs/read_write.c:595 [inline] vfs_write+0x6ac/0x1050 fs/read_write.c:687 ksys_write+0x12a/0x250 fs/read_write.c:739 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x115/0x870 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f3b02d9e0d9 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f3b03bde028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007f3b03025fa0 RCX: 00007f3b02d9e0d9 RDX: 0000000000000007 RSI: 0000200000000200 RDI: 0000000000000004 RBP: 00007f3b02e35024 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f3b03026038 R14: 00007f3b03025fa0 R15: 00007ffd49d97768 </TASK> Modules linked in: ---[ end trace 0000000000000000 ]--- RIP: 0010:wcove_typec_probe+0xdb/0x780 drivers/usb/typec/tcpm/wcove.c:621 Code: 48 c1 ea 03 80 3c 02 00 0f 85 af 05 00 00 48 8d 7d 08 4d 89 af 88 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 7f 05 00 00 49 8d bf 90 00 00 00 48 8b 6d 08 48 RSP: 0018:ffffc9000594fb18 EFLAGS: 00010212 RAX: dffffc0000000000 RBX: ffff88801e371000 RCX: 0000000000000000 RDX: 0000000000000001 RSI: 0000000000000001 RDI: 0000000000000008 RBP: 0000000000000000 R08: 0000000000000004 R09: 0000000000000000 R10: ffff888035b4d483 R11: 0000000000000000 R12: ffffffff90281e28 R13: ffff88801e371010 R14: ffff888035b4d4c0 R15: ffff888035b4d438 FS: 00007f3b03bde6c0(0000) GS:ffff888123ee1000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000562bed817760 CR3: 0000000013036000 CR4: 0000000000350ef0 ---------------- Code disassembly (best guess): 0: 48 c1 ea 03 shr $0x3,%rdx 4: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) 8: 0f 85 af 05 00 00 jne 0x5bd e: 48 8d 7d 08 lea 0x8(%rbp),%rdi 12: 4d 89 af 88 00 00 00 mov %r13,0x88(%r15) 19: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax 20: fc ff df 23: 48 89 fa mov %rdi,%rdx 26: 48 c1 ea 03 shr $0x3,%rdx * 2a: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) <-- trapping instruction 2e: 0f 85 7f 05 00 00 jne 0x5b3 34: 49 8d bf 90 00 00 00 lea 0x90(%r15),%rdi 3b: 48 8b 6d 08 mov 0x8(%rbp),%rbp 3f: 48 rex.W --- 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 [email protected]. 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