[Android 6.1] general protection fault in logi_dj_probe

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7552023a1d74 ANDROID: selftests: wrapfd: Fix test source f..
git tree: android14-6.1
console+strace: https://syzkaller.appspot.com/x/log.txt?x=177c0b69580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c52cbb19e770dedc
dashboard link: https://syzkaller.appspot.com/bug?extid=c5e4c86492426fc6d094
compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10fc0b69580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14f61409580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b9176729660d/disk-7552023a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/16b763bfa3fe/vmlinux-7552023a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2c24f44e7c26/bzImage-7552023a.xz

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

usb 1-1: Manufacturer: syz
general protection fault, probably for non-canonical address 0xdffffc0000000005: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f]
CPU: 1 PID: 37 Comm: kworker/1:1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/15/2026
Workqueue: usb_hub_wq hub_event
RIP: 0010:logi_dj_probe+0x66f/0xf40 drivers/hid/hid-logitech-dj.c:1803
Code: 3e c5 fd 49 83 c7 40 4c 89 f8 48 c1 e8 03 80 3c 18 00 74 08 4c 89 ff e8 3f dc 0a fe 4d 8b 37 49 83 c6 28 4c 89 f0 48 c1 e8 03 <0f> b6 04 18 84 c0 0f 85 a3 08 00 00 41 8b 0e 49 81 c5 e0 18 00 00
RSP: 0018:ffffc9000026ebc8 EFLAGS: 00010206
RAX: 0000000000000005 RBX: dffffc0000000000 RCX: ffff8881092b2880
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc9000026ec18 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff5200004dc9c R12: 0000000000000000
R13: ffff88810b358000 R14: 0000000000000028 R15: ffff888109582040
FS: 0000000000000000(0000) GS:ffff8881f6f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000564d33e0fc18 CR3: 00000001100ae000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
hid_device_probe+0x273/0x410 drivers/hid/hid-core.c:2694
call_driver_probe drivers/base/dd.c:-1 [inline]
really_probe+0x2d7/0x9a0 drivers/base/dd.c:639
__driver_probe_device+0x193/0x270 drivers/base/dd.c:808
driver_probe_device+0x54/0x3e0 drivers/base/dd.c:838
__device_attach_driver+0x2e9/0x4a0 drivers/base/dd.c:966
bus_for_each_drv+0x192/0x220 drivers/base/bus.c:429
__device_attach+0x2b0/0x420 drivers/base/dd.c:1038
device_initial_probe+0x1a/0x20 drivers/base/dd.c:1087
bus_probe_device+0xc0/0x1f0 drivers/base/bus.c:489
device_add+0xb0b/0xec0 drivers/base/core.c:3698
hid_add_device+0x3b8/0x580 drivers/hid/hid-core.c:2848
usbhid_probe+0xc12/0xff0 drivers/hid/usbhid/hid-core.c:1443
usb_probe_interface+0x621/0xb30 drivers/usb/core/driver.c:397
call_driver_probe drivers/base/dd.c:-1 [inline]
really_probe+0x2d7/0x9a0 drivers/base/dd.c:639
__driver_probe_device+0x193/0x270 drivers/base/dd.c:808
driver_probe_device+0x54/0x3e0 drivers/base/dd.c:838
__device_attach_driver+0x2e9/0x4a0 drivers/base/dd.c:966
bus_for_each_drv+0x192/0x220 drivers/base/bus.c:429
__device_attach+0x2b0/0x420 drivers/base/dd.c:1038
device_initial_probe+0x1a/0x20 drivers/base/dd.c:1087
bus_probe_device+0xc0/0x1f0 drivers/base/bus.c:489
device_add+0xb0b/0xec0 drivers/base/core.c:3698
usb_set_configuration+0x1a01/0x1f70 drivers/usb/core/message.c:2223
usb_generic_driver_probe+0x91/0x150 drivers/usb/core/generic.c:238
usb_probe_device+0x154/0x260 drivers/usb/core/driver.c:294
call_driver_probe drivers/base/dd.c:-1 [inline]
really_probe+0x2d7/0x9a0 drivers/base/dd.c:639
__driver_probe_device+0x193/0x270 drivers/base/dd.c:808
driver_probe_device+0x54/0x3e0 drivers/base/dd.c:838
__device_attach_driver+0x2e9/0x4a0 drivers/base/dd.c:966
bus_for_each_drv+0x192/0x220 drivers/base/bus.c:429
__device_attach+0x2b0/0x420 drivers/base/dd.c:1038
device_initial_probe+0x1a/0x20 drivers/base/dd.c:1087
bus_probe_device+0xc0/0x1f0 drivers/base/bus.c:489
device_add+0xb0b/0xec0 drivers/base/core.c:3698
usb_new_device+0x9f4/0x1500 drivers/usb/core/hub.c:2684
hub_port_connect drivers/usb/core/hub.c:5594 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5734 [inline]
port_event drivers/usb/core/hub.c:5898 [inline]
hub_event+0x27fb/0x4310 drivers/usb/core/hub.c:5980
process_one_work+0x717/0xc30 kernel/workqueue.c:2302
worker_thread+0xa4d/0x11d0 kernel/workqueue.c:2449
kthread+0x281/0x320 kernel/kthread.c:386
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:logi_dj_probe+0x66f/0xf40 drivers/hid/hid-logitech-dj.c:1803
Code: 3e c5
----------------
Code disassembly (best guess):
0: 3e c5 fd 49 ds (bad)
4: 83 c7 40 add $0x40,%edi
7: 4c 89 f8 mov %r15,%rax
a: 48 c1 e8 03 shr $0x3,%rax
e: 80 3c 18 00 cmpb $0x0,(%rax,%rbx,1)
12: 74 08 je 0x1c
14: 4c 89 ff mov %r15,%rdi
17: e8 3f dc 0a fe call 0xfe0adc5b
1c: 4d 8b 37 mov (%r15),%r14
1f: 49 83 c6 28 add $0x28,%r14
23: 4c 89 f0 mov %r14,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 0f b6 04 18 movzbl (%rax,%rbx,1),%eax <-- trapping instruction
2e: 84 c0 test %al,%al
30: 0f 85 a3 08 00 00 jne 0x8d9
36: 41 8b 0e mov (%r14),%ecx
39: 49 81 c5 e0 18 00 00 add $0x18e0,%r13


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