Bluetooth: hci2: Dropping invalid advertising data
Bluetooth: hci2: unknown advertising packet type: 0xcc
Bluetooth: hci2: Dropping invalid advertising data
==================================================================
BUG: KASAN: slab-out-of-bounds in hci_le_adv_report_evt net/bluetooth/hci_event.c:5394 [inline]
BUG: KASAN: slab-out-of-bounds in hci_le_meta_evt+0x3754/0x3f20 net/bluetooth/hci_event.c:5694
Read of size 1 at addr ffff8880b3cc4702 by task kworker/u5:2/8122

CPU: 1 PID: 8122 Comm: kworker/u5:2 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Workqueue: hci2 hci_rx_work
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
 print_address_description.cold+0x54/0x219 mm/kasan/report.c:256
 kasan_report_error.cold+0x8a/0x1b9 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:5394 [inline]
 hci_le_meta_evt+0x3754/0x3f20 net/bluetooth/hci_event.c:5694
 hci_event_packet+0x34ad/0x7e20 net/bluetooth/hci_event.c:5959
 hci_rx_work+0x4ad/0xc70 net/bluetooth/hci_core.c:4380
 process_one_work+0x864/0x1570 kernel/workqueue.c:2153
 worker_thread+0x64c/0x1130 kernel/workqueue.c:2296
 kthread+0x33f/0x460 kernel/kthread.c:259
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415

Allocated by task 27191:
 __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 9953:
 __cache_free mm/slab.c:3503 [inline]
 kfree+0xcc/0x210 mm/slab.c:3822
 __rcu_reclaim kernel/rcu/rcu.h:231 [inline]
 rcu_do_batch kernel/rcu/tree.c:2584 [inline]
 invoke_rcu_callbacks kernel/rcu/tree.c:2897 [inline]
 __rcu_process_callbacks kernel/rcu/tree.c:2864 [inline]
 rcu_process_callbacks+0xa0d/0x18b0 kernel/rcu/tree.c:2881
 __do_softirq+0x265/0x980 kernel/softirq.c:292

The buggy address belongs to the object at ffff8880b3cc4500
 which belongs to the cache kmalloc-512 of size 512
The buggy address is located 2 bytes to the right of
 512-byte region [ffff8880b3cc4500, ffff8880b3cc4700)
The buggy address belongs to the page:
page:ffffea0002cf3100 count:1 mapcount:0 mapping:ffff88813bff0940 index:0xffff8880b3cc4000
flags: 0xfff00000000100(slab)
raw: 00fff00000000100 ffffea00022cb088 ffffea00025bcac8 ffff88813bff0940
raw: ffff8880b3cc4000 ffff8880b3cc4000 0000000100000004 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff8880b3cc4600: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff8880b3cc4680: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff8880b3cc4700: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
                   ^
 ffff8880b3cc4780: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff8880b3cc4800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================