kobject: kobject_add_internal failed for hci1:201 with -EEXIST, don't try to register things with the same name in the same directory.
Bluetooth: hci1: failed to register connection device
==================================================================
BUG: KASAN: slab-use-after-free in l2cap_sock_new_connection_cb+0x208/0x2f0
Read of size 8 at addr ffff888112c527b0 by task kworker/u11:1/16197

CPU: 1 UID: 0 PID: 16197 Comm: kworker/u11:1 Tainted: G             L      syzkaller #0 PREEMPT_{RT,(full)} 
Tainted: [L]=SOFTLOCKUP
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Workqueue: hci1 hci_rx_work
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150
 print_address_description+0x55/0x1e0
 print_report+0x58/0x70
 kasan_report+0x117/0x150
 l2cap_sock_new_connection_cb+0x208/0x2f0
 l2cap_connect_cfm+0x368/0x1560
 hci_connect_cfm+0x95/0x140
 le_conn_complete_evt+0x1134/0x16b0
 hci_le_conn_complete_evt+0x187/0x470
 hci_event_packet+0x659/0xef0
 hci_rx_work+0x3ee/0x1040
 process_one_work+0x98b/0x1630
 worker_thread+0xb49/0x1140
 kthread+0x388/0x470
 ret_from_fork+0x514/0xb70
 ret_from_fork_asm+0x1a/0x30
 </TASK>

Allocated by task 16197:
 kasan_save_track+0x3e/0x80
 __kasan_kmalloc+0x93/0xb0
 __kmalloc_noprof+0x3e7/0x7b0
 sk_prot_alloc+0xe7/0x210
 sk_alloc+0x3a/0x390
 bt_sock_alloc+0x3b/0x310
 l2cap_sock_new_connection_cb+0xf1/0x2f0
 l2cap_connect_cfm+0x368/0x1560
 hci_connect_cfm+0x95/0x140
 le_conn_complete_evt+0x1134/0x16b0
 hci_le_conn_complete_evt+0x187/0x470
 hci_event_packet+0x659/0xef0
 hci_rx_work+0x3ee/0x1040
 process_one_work+0x98b/0x1630
 worker_thread+0xb49/0x1140
 kthread+0x388/0x470
 ret_from_fork+0x514/0xb70
 ret_from_fork_asm+0x1a/0x30

Freed by task 21575:
 kasan_save_track+0x3e/0x80
 kasan_save_free_info+0x46/0x50
 __kasan_slab_free+0x5c/0x80
 kfree+0x1c5/0x6c0
 __sk_destruct+0x74b/0x9d0
 l2cap_sock_cleanup_listen+0xe0/0x440
 l2cap_sock_release+0x6e/0x270
 __sock_release+0xb9/0x250
 sock_close+0x1c/0x30
 __fput+0x461/0xa70
 task_work_run+0x1d9/0x270
 get_signal+0x11eb/0x1330
 arch_do_signal_or_restart+0xbc/0x840
 exit_to_user_mode_loop+0x8c/0x4d0
 do_syscall_64+0x33e/0xf80
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

The buggy address belongs to the object at ffff888112c52000
 which belongs to the cache kmalloc-2k of size 2048
The buggy address is located 1968 bytes inside of
 freed 2048-byte region [ffff888112c52000, ffff888112c52800)

The buggy address belongs to the physical page:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x112c50
head: order:3 mapcount:0 entire_mapcount:0 nr_pages_mapped:0 pincount:0
flags: 0x100000000000040(head|node=0|zone=2)
page_type: f5(slab)
raw: 0100000000000040 ffff888100042000 dead000000000100 dead000000000122
raw: 0000000000000000 0000000800080008 00000000f5000000 0000000000000000
head: 0100000000000040 ffff888100042000 dead000000000100 dead000000000122
head: 0000000000000000 0000000800080008 00000000f5000000 0000000000000000
head: 0100000000000003 fffffffffffffe01 00000000ffffffff 00000000ffffffff
head: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000008
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 3, migratetype Unmovable, gfp_mask 0xd20c0(__GFP_IO|__GFP_FS|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC), pid 1, tgid 1 (swapper/0), ts 15305707847, free_ts 0
 post_alloc_hook+0x1f9/0x250
 get_page_from_freelist+0x27d6/0x2850
 __alloc_frozen_pages_noprof+0x18d/0x380
 allocate_slab+0x74/0x5e0
 refill_objects+0x33c/0x3d0
 __pcs_replace_empty_main+0x373/0x720
 __kvmalloc_node_noprof+0x6f4/0x8e0
 v4l2_ctrl_new+0x105d/0x1860
 v4l2_ctrl_new_custom+0x5fc/0x850
 vivid_create_controls+0xe21/0x3bd0
 vivid_probe+0x425f/0x72c0
 platform_probe+0xf9/0x190
 really_probe+0x267/0xaf0
 __driver_probe_device+0x1e2/0x350
 driver_probe_device+0x4f/0x240
 __driver_attach+0x33c/0x600
page_owner free stack trace missing

Memory state around the buggy address:
 ffff888112c52680: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
 ffff888112c52700: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff888112c52780: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
                                     ^
 ffff888112c52800: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
 ffff888112c52880: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
==================================================================
