Bluetooth: hci1: Dropping invalid advertising data
Bluetooth: hci1: Dropping invalid advertising data
Bluetooth: hci1: 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 ffff88809d692a41 by task kworker/u5:3/8136

CPU: 1 PID: 8136 Comm: kworker/u5:3 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Workqueue: hci1 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 22197:
 __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 21328:
 __cache_free mm/slab.c:3503 [inline]
 kfree+0xcc/0x210 mm/slab.c:3822
 skb_free_head net/core/skbuff.c:563 [inline]
 skb_release_data+0x6de/0x920 net/core/skbuff.c:583
 skb_release_all net/core/skbuff.c:640 [inline]
 __kfree_skb+0x46/0x60 net/core/skbuff.c:654
 tcp_rcv_established+0x13eb/0x1ef0 net/ipv4/tcp_input.c:5595
 tcp_v4_do_rcv+0x5d6/0x870 net/ipv4/tcp_ipv4.c:1547
 tcp_v4_rcv+0x2c03/0x3b80 net/ipv4/tcp_ipv4.c:1832
 ip_local_deliver_finish+0x495/0xc00 net/ipv4/ip_input.c:215
 NF_HOOK include/linux/netfilter.h:289 [inline]
 ip_local_deliver+0x188/0x500 net/ipv4/ip_input.c:256
 dst_input include/net/dst.h:461 [inline]
 ip_rcv_finish+0x1ca/0x2e0 net/ipv4/ip_input.c:414
 NF_HOOK include/linux/netfilter.h:289 [inline]
 ip_rcv+0xca/0x3c0 net/ipv4/ip_input.c:524
 __netif_receive_skb_one_core+0x114/0x180 net/core/dev.c:4954
 __netif_receive_skb+0x27/0x1c0 net/core/dev.c:5066
 netif_receive_skb_internal+0xf0/0x3f0 net/core/dev.c:5156
 napi_skb_finish net/core/dev.c:5601 [inline]
 napi_gro_receive+0x2e6/0x450 net/core/dev.c:5632
 receive_buf+0xc2c/0x6780 drivers/net/virtio_net.c:1088
 virtnet_receive drivers/net/virtio_net.c:1352 [inline]
 virtnet_poll+0x568/0xe00 drivers/net/virtio_net.c:1457
 napi_poll net/core/dev.c:6280 [inline]
 net_rx_action+0x4ac/0xfb0 net/core/dev.c:6346
 __do_softirq+0x265/0x980 kernel/softirq.c:292

The buggy address belongs to the object at ffff88809d692840
 which belongs to the cache kmalloc-512 of size 512
The buggy address is located 1 bytes to the right of
 512-byte region [ffff88809d692840, ffff88809d692a40)
The buggy address belongs to the page:
page:ffffea000275a480 count:1 mapcount:0 mapping:ffff88813bff0940 index:0x0
flags: 0xfff00000000100(slab)
raw: 00fff00000000100 ffffea0002611348 ffffea000263db48 ffff88813bff0940
raw: 0000000000000000 ffff88809d6920c0 0000000100000006 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff88809d692900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff88809d692980: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff88809d692a00: 00 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc
                                           ^
 ffff88809d692a80: fc fc fc fc fc fc fc fc 00 00 00 00 00 00 00 00
 ffff88809d692b00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================