Bluetooth: hci5: unknown advertising packet type: 0xc0 Bluetooth: hci5: Dropping invalid advertising data Bluetooth: hci5: advertising data len corrected Bluetooth: hci5: unknown advertising packet type: 0xad ================================================================== BUG: KASAN: slab-out-of-bounds in hci_le_adv_report_evt net/bluetooth/hci_event.c:5335 [inline] BUG: KASAN: slab-out-of-bounds in hci_le_meta_evt+0x3428/0x3a50 net/bluetooth/hci_event.c:5637 FAT-fs (loop4): invalid media value (0x00) Read of size 1 at addr ffff888054977706 by task kworker/u5:1/7723 CPU: 0 PID: 7723 Comm: kworker/u5:1 Not tainted 4.19.138-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: hci5 hci_rx_work Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1fc/0x2fe lib/dump_stack.c:118 print_address_description.cold+0x54/0x219 mm/kasan/report.c:256 kasan_report_error.cold+0x8a/0x1c7 mm/kasan/report.c:354 kasan_report mm/kasan/report.c:412 [inline] __asan_report_load1_noabort+0x88/0x90 mm/kasan/report.c:430 hci_le_adv_report_evt net/bluetooth/hci_event.c:5335 [inline] hci_le_meta_evt+0x3428/0x3a50 net/bluetooth/hci_event.c:5637 FAT-fs (loop4): Can't find a valid FAT filesystem hci_event_packet+0x1a29/0x858f net/bluetooth/hci_event.c:5897 hci_rx_work+0x46b/0xa90 net/bluetooth/hci_core.c:4359 process_one_work+0x864/0x1570 kernel/workqueue.c:2155 worker_thread+0x64c/0x1130 kernel/workqueue.c:2298 kthread+0x30b/0x410 kernel/kthread.c:246 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415 Allocated by task 10631: __do_kmalloc_node mm/slab.c:3689 [inline] __kmalloc_node_track_caller+0x4c/0x70 mm/slab.c:3703 __kmalloc_reserve net/core/skbuff.c:137 [inline] __alloc_skb+0xae/0x560 net/core/skbuff.c:205 alloc_skb include/linux/skbuff.h:995 [inline] bt_skb_alloc include/net/bluetooth/bluetooth.h:339 [inline] vhci_get_user drivers/bluetooth/hci_vhci.c:180 [inline] vhci_write+0xbd/0x450 drivers/bluetooth/hci_vhci.c:299 call_write_iter include/linux/fs.h:1821 [inline] new_sync_write fs/read_write.c:474 [inline] __vfs_write+0x51b/0x770 fs/read_write.c:487 vfs_write+0x1f3/0x540 fs/read_write.c:549 ksys_write+0x12b/0x2a0 fs/read_write.c:599 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe Freed by task 3707: __cache_free mm/slab.c:3503 [inline] kfree+0xcc/0x210 mm/slab.c:3822 kernfs_fop_release+0x120/0x190 fs/kernfs/file.c:783 __fput+0x2ce/0x890 fs/file_table.c:278 task_work_run+0x148/0x1c0 kernel/task_work.c:113 tracehook_notify_resume include/linux/tracehook.h:193 [inline] exit_to_usermode_loop+0x251/0x2a0 arch/x86/entry/common.c:167 prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline] syscall_return_slowpath arch/x86/entry/common.c:271 [inline] do_syscall_64+0x538/0x620 arch/x86/entry/common.c:296 entry_SYSCALL_64_after_hwframe+0x49/0xbe The buggy address belongs to the object at ffff888054977500 which belongs to the cache kmalloc-512 of size 512 The buggy address is located 6 bytes to the right of 512-byte region [ffff888054977500, ffff888054977700) The buggy address belongs to the page: page:ffffea0001525dc0 count:1 mapcount:0 mapping:ffff88812c39c940 index:0x0 flags: 0xfffe0000000100(slab) raw: 00fffe0000000100 ffffea00016a2448 ffffea0000cee848 ffff88812c39c940 raw: 0000000000000000 ffff888054977000 0000000100000006 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff888054977600: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff888054977680: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffff888054977700: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ^ ffff888054977780: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff888054977800: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ==================================================================