Hello, syzbot found the following issue on: HEAD commit: 226ff2e681d0 usb: typec: ucsi: Convert connector specific .. git tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing console output: https://syzkaller.appspot.com/x/log.txt?x=169619f7980000 kernel config: https://syzkaller.appspot.com/x/.config?x=358c1689354aeef3 dashboard link: https://syzkaller.appspot.com/bug?extid=3fa2af55f15bd21cada9 compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/e48f2af8afd7/disk-226ff2e6.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/76328e28b54c/vmlinux-226ff2e6.xz kernel image: https://storage.googleapis.com/syzbot-assets/ab9f75a466a2/bzImage-226ff2e6.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+3fa2af55f15bd21cada9@xxxxxxxxxxxxxxxxxxxxxxxxx ------------[ cut here ]------------ UBSAN: shift-out-of-bounds in drivers/hid/hid-core.c:1352:16 shift exponent 4294967295 is too large for 32-bit type 'int' CPU: 1 UID: 0 PID: 31701 Comm: kworker/1:9 Not tainted 6.12.0-rc6-syzkaller-00103-g226ff2e681d0 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Workqueue: usb_hub_wq hub_event Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 ubsan_epilogue lib/ubsan.c:231 [inline] __ubsan_handle_shift_out_of_bounds+0x2a5/0x480 lib/ubsan.c:468 s32ton.cold+0x37/0x9c drivers/hid/hid-core.c:1352 hid_set_field+0x1e0/0x370 drivers/hid/hid-core.c:1905 hidinput_input_event+0x290/0x430 drivers/hid/hid-input.c:1865 input_event_dispose drivers/input/input.c:321 [inline] input_handle_event+0x14e/0x14d0 drivers/input/input.c:369 input_inject_event+0x1bb/0x370 drivers/input/input.c:428 __led_set_brightness drivers/leds/led-core.c:52 [inline] led_set_brightness_nopm drivers/leds/led-core.c:323 [inline] led_set_brightness_nosleep drivers/leds/led-core.c:354 [inline] led_set_brightness+0x211/0x290 drivers/leds/led-core.c:316 kbd_led_trigger_activate+0xcb/0x110 drivers/tty/vt/keyboard.c:1036 led_trigger_set+0x59a/0xc60 drivers/leds/led-triggers.c:212 led_match_default_trigger drivers/leds/led-triggers.c:269 [inline] led_match_default_trigger drivers/leds/led-triggers.c:263 [inline] led_trigger_set_default drivers/leds/led-triggers.c:287 [inline] led_trigger_set_default+0x1bd/0x2a0 drivers/leds/led-triggers.c:276 led_classdev_register_ext+0x78c/0x9e0 drivers/leds/led-class.c:555 led_classdev_register include/linux/leds.h:273 [inline] input_leds_connect+0x552/0x8e0 drivers/input/input-leds.c:145 input_attach_handler.isra.0+0x181/0x260 drivers/input/input.c:1027 input_register_device+0xa84/0x1110 drivers/input/input.c:2470 hidinput_connect+0x1d9c/0x2ba0 drivers/hid/hid-input.c:2343 hid_connect+0x13a8/0x18a0 drivers/hid/hid-core.c:2234 hid_hw_start drivers/hid/hid-core.c:2349 [inline] hid_hw_start+0xaa/0x140 drivers/hid/hid-core.c:2340 ms_probe+0x195/0x500 drivers/hid/hid-microsoft.c:391 __hid_device_probe drivers/hid/hid-core.c:2699 [inline] hid_device_probe+0x2eb/0x490 drivers/hid/hid-core.c:2736 call_driver_probe drivers/base/dd.c:579 [inline] really_probe+0x23e/0xa90 drivers/base/dd.c:658 __driver_probe_device+0x1de/0x440 drivers/base/dd.c:800 driver_probe_device+0x4c/0x1b0 drivers/base/dd.c:830 __device_attach_driver+0x1df/0x310 drivers/base/dd.c:958 bus_for_each_drv+0x157/0x1e0 drivers/base/bus.c:459 __device_attach+0x1e8/0x4b0 drivers/base/dd.c:1030 bus_probe_device+0x17f/0x1c0 drivers/base/bus.c:534 device_add+0x114b/0x1a70 drivers/base/core.c:3672 hid_add_device+0x37f/0xa70 drivers/hid/hid-core.c:2882 usbhid_probe+0xd3b/0x1410 drivers/hid/usbhid/hid-core.c:1431 usb_probe_interface+0x309/0x9d0 drivers/usb/core/driver.c:399 call_driver_probe drivers/base/dd.c:579 [inline] really_probe+0x23e/0xa90 drivers/base/dd.c:658 __driver_probe_device+0x1de/0x440 drivers/base/dd.c:800 driver_probe_device+0x4c/0x1b0 drivers/base/dd.c:830 __device_attach_driver+0x1df/0x310 drivers/base/dd.c:958 bus_for_each_drv+0x157/0x1e0 drivers/base/bus.c:459 __device_attach+0x1e8/0x4b0 drivers/base/dd.c:1030 bus_probe_device+0x17f/0x1c0 drivers/base/bus.c:534 device_add+0x114b/0x1a70 drivers/base/core.c:3672 usb_set_configuration+0x10cb/0x1c50 drivers/usb/core/message.c:2210 usb_generic_driver_probe+0xb1/0x110 drivers/usb/core/generic.c:254 usb_probe_device+0xec/0x3e0 drivers/usb/core/driver.c:294 call_driver_probe drivers/base/dd.c:579 [inline] really_probe+0x23e/0xa90 drivers/base/dd.c:658 __driver_probe_device+0x1de/0x440 drivers/base/dd.c:800 driver_probe_device+0x4c/0x1b0 drivers/base/dd.c:830 __device_attach_driver+0x1df/0x310 drivers/base/dd.c:958 bus_for_each_drv+0x157/0x1e0 drivers/base/bus.c:459 __device_attach+0x1e8/0x4b0 drivers/base/dd.c:1030 bus_probe_device+0x17f/0x1c0 drivers/base/bus.c:534 device_add+0x114b/0x1a70 drivers/base/core.c:3672 usb_new_device+0xd90/0x1a10 drivers/usb/core/hub.c:2651 hub_port_connect drivers/usb/core/hub.c:5521 [inline] hub_port_connect_change drivers/usb/core/hub.c:5661 [inline] port_event drivers/usb/core/hub.c:5821 [inline] hub_event+0x2e58/0x4f40 drivers/usb/core/hub.c:5903 process_one_work+0x9c5/0x1ba0 kernel/workqueue.c:3229 process_scheduled_works kernel/workqueue.c:3310 [inline] worker_thread+0x6c8/0xf00 kernel/workqueue.c:3391 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </TASK> ---[ end trace ]--- --- 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 syzkaller@xxxxxxxxxxxxxxxx. 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
