ir-kbd-i2c 0-0071: IR for HDPVR is known to cause problems during recording, use enable_hdpvr modparam to enable ================================================================== BUG: KASAN: global-out-of-bounds in hdpvr_probe.cold+0x11b3/0x1247 drivers/media/usb/hdpvr/hdpvr-core.c:371 Read of size 4 at addr ffffffff87788480 by task kworker/1:4/2894 CPU: 1 PID: 2894 Comm: kworker/1:4 Not tainted 5.2.0-rc6+ #1 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: usb_hub_wq hub_event Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0xca/0x13e lib/dump_stack.c:113 print_address_description+0x67/0x231 mm/kasan/report.c:188 __kasan_report.cold+0x1a/0x32 mm/kasan/report.c:317 kasan_report+0xe/0x20 mm/kasan/common.c:614 hdpvr_probe.cold+0x11b3/0x1247 drivers/media/usb/hdpvr/hdpvr-core.c:371 usb_probe_interface+0x305/0x7a0 drivers/usb/core/driver.c:361 really_probe+0x281/0x660 drivers/base/dd.c:509 driver_probe_device+0x104/0x210 drivers/base/dd.c:670 __device_attach_driver+0x1c2/0x220 drivers/base/dd.c:777 bus_for_each_drv+0x15c/0x1e0 drivers/base/bus.c:454 __device_attach+0x217/0x360 drivers/base/dd.c:843 bus_probe_device+0x1e4/0x290 drivers/base/bus.c:514 device_add+0xae6/0x16f0 drivers/base/core.c:2111 usb_set_configuration+0xdf6/0x1670 drivers/usb/core/message.c:2023 generic_probe+0x9d/0xd5 drivers/usb/core/generic.c:210 usb_probe_device+0x99/0x100 drivers/usb/core/driver.c:266 really_probe+0x281/0x660 drivers/base/dd.c:509 driver_probe_device+0x104/0x210 drivers/base/dd.c:670 __device_attach_driver+0x1c2/0x220 drivers/base/dd.c:777 bus_for_each_drv+0x15c/0x1e0 drivers/base/bus.c:454 __device_attach+0x217/0x360 drivers/base/dd.c:843 bus_probe_device+0x1e4/0x290 drivers/base/bus.c:514 device_add+0xae6/0x16f0 drivers/base/core.c:2111 usb_new_device.cold+0x8c1/0x1016 drivers/usb/core/hub.c:2534 hub_port_connect drivers/usb/core/hub.c:5089 [inline] hub_port_connect_change drivers/usb/core/hub.c:5204 [inline] port_event drivers/usb/core/hub.c:5350 [inline] hub_event+0x1ada/0x3590 drivers/usb/core/hub.c:5432 process_one_work+0x905/0x1570 kernel/workqueue.c:2269 process_scheduled_works kernel/workqueue.c:2331 [inline] worker_thread+0x7ab/0xe20 kernel/workqueue.c:2417 kthread+0x30b/0x410 kernel/kthread.c:255 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:352 The buggy address belongs to the variable: video_nr+0x20/0x1be0 Memory state around the buggy address: ffffffff87788380: fa fa fa fa 04 fa fa fa fa fa fa fa 04 fa fa fa ffffffff87788400: fa fa fa fa 04 fa fa fa fa fa fa fa 00 00 00 00 >ffffffff87788480: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00 ^ ffffffff87788500: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffffffff87788580: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================