==================================================================
BUG: KASAN: slab-out-of-bounds in memcpy include/linux/string.h:373 [inline]
BUG: KASAN: slab-out-of-bounds in hci_inquiry_result_evt net/bluetooth/hci_event.c:2375 [inline]
BUG: KASAN: slab-out-of-bounds in hci_event_packet+0x3dbf/0x858f net/bluetooth/hci_event.c:5747
Read of size 3 at addr ffff8880a49924bf by task kworker/u5:2/7769

CPU: 1 PID: 7769 Comm: kworker/u5:2 Not tainted 4.19.136-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: hci3 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+0x8f/0x96 mm/kasan/report.c:412
 memcpy+0x20/0x50 mm/kasan/kasan.c:302
 memcpy include/linux/string.h:373 [inline]
 hci_inquiry_result_evt net/bluetooth/hci_event.c:2375 [inline]
 hci_event_packet+0x3dbf/0x858f net/bluetooth/hci_event.c:5747
 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 7135:
 __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 6022:
 __cache_free mm/slab.c:3503 [inline]
 kfree+0xcc/0x210 mm/slab.c:3822
 load_elf_binary+0x2349/0x5050 fs/binfmt_elf.c:1117
 search_binary_handler.part.0+0xf9/0x4e0 fs/exec.c:1655
 search_binary_handler fs/exec.c:1644 [inline]
 exec_binprm fs/exec.c:1697 [inline]
 __do_execve_file+0x1357/0x2360 fs/exec.c:1819
 do_execveat_common fs/exec.c:1866 [inline]
 do_execve+0x35/0x50 fs/exec.c:1883
 call_usermodehelper_exec_async+0x4b0/0x630 kernel/umh.c:107
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415

The buggy address belongs to the object at ffff8880a49922c0
 which belongs to the cache kmalloc-512 of size 512
The buggy address is located 511 bytes inside of
 512-byte region [ffff8880a49922c0, ffff8880a49924c0)
The buggy address belongs to the page:
page:ffffea0002926480 count:1 mapcount:0 mapping:ffff88812c39c940 index:0xffff8880a4992a40
flags: 0xfffe0000000100(slab)
raw: 00fffe0000000100 ffffea000253b688 ffffea0002937348 ffff88812c39c940
raw: ffff8880a4992a40 ffff8880a4992040 0000000100000003 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff8880a4992380: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff8880a4992400: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff8880a4992480: 00 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc
                                           ^
 ffff8880a4992500: fc fc fc fc fc fc fc fc fb fb fb fb fb fb fb fb
 ffff8880a4992580: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================