[syzbot] [input?] general protection fault in rmi_driver_suspend
syzbot <[email protected]> Wed, 05 Aug 2026 17:01:31 -0700
| Newsgroups | org.kernel.vger.linux-input,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
Hello, syzbot found the following issue on: HEAD commit: 848acc8ffe1b Merge tag 'fsverity-for-linus' of git://git.k.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=12094bb9580000 kernel config: https://syzkaller.appspot.com/x/.config?x=cb17729fb04b1e3a dashboard link: https://syzkaller.appspot.com/bug?extid=09103639e39c989e3ed3 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=17b27649580000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/375d27e96ecb/disk-848acc8f.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/4ba19a656b9d/vmlinux-848acc8f.xz kernel image: https://storage.googleapis.com/syzbot-assets/7c2a17aaee7c/bzImage-848acc8f.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 0xdffffc000000000f: 0000 [#1] SMP KASAN PTI KASAN: null-ptr-deref in range [0x0000000000000078-0x000000000000007f] CPU: 1 UID: 0 PID: 1035 Comm: kworker/u8:8 Not tainted syzkaller #0 PREEMPT_{RT,(full)} Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026 Workqueue: pm pm_runtime_work RIP: 0010:dev_get_drvdata include/linux/device.h:989 [inline] RIP: 0010:rmi_suspend_functions drivers/input/rmi4/rmi_driver.c:283 [inline] RIP: 0010:rmi_driver_suspend+0x30/0x180 drivers/input/rmi4/rmi_driver.c:994 Code: 57 41 56 41 55 41 54 53 50 89 74 24 04 48 89 fb 48 bd 00 00 00 00 00 fc ff df e8 6b c7 5e fa 4c 8d 73 78 4c 89 f0 48 c1 e8 03 <80> 3c 28 00 74 08 4c 89 f7 e8 e2 3a c8 fa 4d 8b 36 4c 89 f0 48 c1 RSP: 0018:ffffc90005f67670 EFLAGS: 00010206 RAX: 000000000000000f RBX: 0000000000000000 RCX: ffff888027c58000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: dffffc0000000000 R08: 0000000000000000 R09: 0000000000000000 R10: dffffc0000000000 R11: ffffffff88838110 R12: dffffc0000000000 R13: 0000000000000003 R14: 0000000000000078 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff888125d3e000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000001b2cc63fff CR3: 000000003c77c000 CR4: 00000000003526f0 Call Trace: <TASK> rmi_suspend+0xa7/0xf0 drivers/hid/hid-rmi.c:448 hid_suspend+0x4a3/0x530 drivers/hid/usbhid/hid-core.c:1618 usb_suspend_interface drivers/usb/core/driver.c:1323 [inline] usb_suspend_both+0x285/0x1040 drivers/usb/core/driver.c:1446 usb_runtime_suspend+0x58/0x110 drivers/usb/core/driver.c:2000 __rpm_callback+0x2d6/0x930 drivers/base/power/runtime.c:406 rpm_callback drivers/base/power/runtime.c:460 [inline] rpm_suspend+0x8a0/0x17a0 drivers/base/power/runtime.c:698 pm_runtime_work+0x132/0x1b0 drivers/base/power/runtime.c:-1 process_one_work kernel/workqueue.c:3322 [inline] process_scheduled_works+0xa8e/0x14e0 kernel/workqueue.c:3405 worker_thread+0xa47/0xfb0 kernel/workqueue.c:3486 kthread+0x388/0x470 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: ---[ end trace 0000000000000000 ]--- RIP: 0010:dev_get_drvdata include/linux/device.h:989 [inline] RIP: 0010:rmi_suspend_functions drivers/input/rmi4/rmi_driver.c:283 [inline] RIP: 0010:rmi_driver_suspend+0x30/0x180 drivers/input/rmi4/rmi_driver.c:994 Code: 57 41 56 41 55 41 54 53 50 89 74 24 04 48 89 fb 48 bd 00 00 00 00 00 fc ff df e8 6b c7 5e fa 4c 8d 73 78 4c 89 f0 48 c1 e8 03 <80> 3c 28 00 74 08 4c 89 f7 e8 e2 3a c8 fa 4d 8b 36 4c 89 f0 48 c1 RSP: 0018:ffffc90005f67670 EFLAGS: 00010206 RAX: 000000000000000f RBX: 0000000000000000 RCX: ffff888027c58000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: dffffc0000000000 R08: 0000000000000000 R09: 0000000000000000 R10: dffffc0000000000 R11: ffffffff88838110 R12: dffffc0000000000 R13: 0000000000000003 R14: 0000000000000078 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff888125d3e000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000001b2cc63fff CR3: 000000003c77c000 CR4: 00000000003526f0 ---------------- Code disassembly (best guess): 0: 57 push %rdi 1: 41 56 push %r14 3: 41 55 push %r13 5: 41 54 push %r12 7: 53 push %rbx 8: 50 push %rax 9: 89 74 24 04 mov %esi,0x4(%rsp) d: 48 89 fb mov %rdi,%rbx 10: 48 bd 00 00 00 00 00 movabs $0xdffffc0000000000,%rbp 17: fc ff df 1a: e8 6b c7 5e fa call 0xfa5ec78a 1f: 4c 8d 73 78 lea 0x78(%rbx),%r14 23: 4c 89 f0 mov %r14,%rax 26: 48 c1 e8 03 shr $0x3,%rax * 2a: 80 3c 28 00 cmpb $0x0,(%rax,%rbp,1) <-- trapping instruction 2e: 74 08 je 0x38 30: 4c 89 f7 mov %r14,%rdi 33: e8 e2 3a c8 fa call 0xfac83b1a 38: 4d 8b 36 mov (%r14),%r14 3b: 4c 89 f0 mov %r14,%rax 3e: 48 rex.W 3f: c1 .byte 0xc1 --- 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 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