[Android 6.1] UBSAN: shift-out-of-bounds in s32ton

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 50ba6c46f3ac ANDROID: GKI: Update symbol list for telechips
git tree: android14-6.1
console output: https://syzkaller.appspot.com/x/log.txt?x=1650c412580000
kernel config: https://syzkaller.appspot.com/x/.config?x=94b6faff0324964a
dashboard link: https://syzkaller.appspot.com/bug?extid=eec5b146521c20a05929
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1352b812580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=166d117c580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c2cf77cb76fb/disk-50ba6c46.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c7bd18f78e6c/vmlinux-50ba6c46.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5285dc1d75d4/bzImage-50ba6c46.xz

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

microsoft 0003:045E:07DA.0001: unknown main item tag 0x0
microsoft 0003:045E:07DA.0001: unknown main item tag 0x0
microsoft 0003:045E:07DA.0001: unknown main item tag 0x0
microsoft 0003:045E:07DA.0001: unsupported Resolution Multiplier 0
================================================================================
UBSAN: shift-out-of-bounds in drivers/hid/hid-core.c:1351:16
shift exponent 4294967295 is too large for 32-bit type '__s32' (aka 'int')
CPU: 1 PID: 39 Comm: kworker/1:1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Workqueue: usb_hub_wq hub_event
Call Trace:
<TASK>
__dump_stack+0x21/0x24 lib/dump_stack.c:88
dump_stack_lvl+0xee/0x150 lib/dump_stack.c:106
dump_stack+0x15/0x24 lib/dump_stack.c:113
ubsan_epilogue+0xe/0x40 lib/ubsan.c:151
__ubsan_handle_shift_out_of_bounds+0x37c/0x400 lib/ubsan.c:321
s32ton+0xe8/0x150 drivers/hid/hid-core.c:1351
hid_output_field drivers/hid/hid-core.c:1829 [inline]
hid_output_report+0x423/0x780 drivers/hid/hid-core.c:1861
__hid_request+0x152/0x450 drivers/hid/hid-core.c:1959
hidinput_change_resolution_multipliers drivers/hid/hid-input.c:1951 [inline]
hidinput_connect+0x22c4/0x31b0 drivers/hid/hid-input.c:2328
hid_connect+0x496/0x1960 drivers/hid/hid-core.c:2191
hid_hw_start+0xbf/0x150 drivers/hid/hid-core.c:2304
ms_probe+0x190/0x460 drivers/hid/hid-microsoft.c:391
hid_device_probe+0x268/0x390 drivers/hid/hid-core.c:2635
call_driver_probe drivers/base/dd.c:-1 [inline]
really_probe+0x2cb/0x960 drivers/base/dd.c:639
__driver_probe_device+0x198/0x280 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+0x183/0x210 drivers/base/bus.c:429
__device_attach+0x2a2/0x400 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+0xb4d/0xef0 drivers/base/core.c:3698
hid_add_device+0x38f/0x540 drivers/hid/hid-core.c:2787
usbhid_probe+0xbb6/0xfa0 drivers/hid/usbhid/hid-core.c:1427
usb_probe_interface+0x610/0xaf0 drivers/usb/core/driver.c:397
call_driver_probe drivers/base/dd.c:-1 [inline]
really_probe+0x2cb/0x960 drivers/base/dd.c:639
__driver_probe_device+0x198/0x280 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+0x183/0x210 drivers/base/bus.c:429
__device_attach+0x2a2/0x400 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+0xb4d/0xef0 drivers/base/core.c:3698
usb_set_configuration+0x19c2/0x1f10 drivers/usb/core/message.c:2165
usb_generic_driver_probe+0x91/0x150 drivers/usb/core/generic.c:238
usb_probe_device+0x159/0x270 drivers/usb/core/driver.c:294
call_driver_probe drivers/base/dd.c:-1 [inline]
really_probe+0x2cb/0x960 drivers/base/dd.c:639
__driver_probe_device+0x198/0x280 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+0x183/0x210 drivers/base/bus.c:429
__device_attach+0x2a2/0x400 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+0xb4d/0xef0 drivers/base/core.c:3698
usb_new_device+0xa70/0x1520 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+0x2850/0x4350 drivers/usb/core/hub.c:5980
process_one_work+0x71f/0xc40 kernel/workqueue.c:2302
worker_thread+0xa29/0x11f0 kernel/workqueue.c:2449
kthread+0x281/0x320 kernel/kthread.c:386
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
================================================================================
microsoft 0003:045E:07DA.0001: No inputs registered, leaving
microsoft 0003:045E:07DA.0001: hidraw0: USB HID v0.00 Device [HID 045e:07da] on usb-dummy_hcd.2-1/input0
microsoft 0003:045E:07DA.0001: no inputs found
microsoft 0003:045E:07DA.0001: could not initialize ff, continuing anyway
usb 3-1: USB disconnect, device number 2


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