Bluetooth: hci4: command 0x0419 tx timeout
Bluetooth: hci5: command 0x0419 tx timeout
Bluetooth: hci3: command 0x0419 tx timeout
==================================================================
BUG: KASAN: use-after-free in __lock_acquire+0x42c9/0x5e70
Read of size 8 at addr ffff88800f25d458 by task kmemleak/55

CPU: 1 PID: 55 Comm: kmemleak Not tainted 6.0.0-rc7-next-20220928 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
Call Trace:
 <TASK>
 dump_stack_lvl+0x8b/0xb3
 print_report+0x172/0x475
 kasan_report+0xbb/0x1c0
 __lock_acquire+0x42c9/0x5e70
 lock_acquire+0x1a2/0x530
 _raw_spin_lock_irq+0x32/0x50
 kmemleak_scan+0x21d/0x16d0
 kmemleak_scan_thread+0x8f/0xb1
 kthread+0x2ed/0x3a0
 ret_from_fork+0x22/0x30
 </TASK>

Allocated by task 828:
 kasan_save_stack+0x1e/0x40
 kasan_set_track+0x21/0x30
 __kasan_slab_alloc+0x58/0x70
 kmem_cache_alloc+0x1a9/0x3e0
 __create_object+0x3d/0xc10
 kmem_cache_alloc+0x235/0x3e0
 mas_alloc_nodes+0x420/0x800
 mas_preallocate+0x1bb/0x360
 mmap_region+0x774/0x1a00
 do_mmap+0x828/0xf40
 vm_mmap_pgoff+0x1af/0x270
 vm_mmap+0x95/0xc0
 elf_map+0x188/0x2b0
 load_elf_binary+0xd89/0x4ef0
 bprm_execve+0x7f5/0x1920
 kernel_execve+0x3ea/0x500
 call_usermodehelper_exec_async+0x2e6/0x580
 ret_from_fork+0x22/0x30

Freed by task 821:
 kasan_save_stack+0x1e/0x40
 kasan_set_track+0x21/0x30
 kasan_save_free_info+0x2a/0x50
 __kasan_slab_free+0x106/0x190
 kmem_cache_free+0xf7/0x610
 rcu_core+0x7e2/0x2080
 __do_softirq+0x1c3/0x8f5

Last potentially related work creation:
 kasan_save_stack+0x1e/0x40
 __kasan_record_aux_stack+0x95/0xb0
 call_rcu+0x6a/0xa30
 kmem_cache_free+0xbd/0x610
 mas_destroy+0x2cd/0x560
 mas_store_prealloc+0xf0/0x160
 mmap_region+0xdc5/0x1a00
 do_mmap+0x828/0xf40
 vm_mmap_pgoff+0x1af/0x270
 vm_mmap+0x95/0xc0
 elf_map+0x188/0x2b0
 load_elf_binary+0xd89/0x4ef0
 bprm_execve+0x7f5/0x1920
 kernel_execve+0x3ea/0x500
 call_usermodehelper_exec_async+0x2e6/0x580
 ret_from_fork+0x22/0x30

Second to last potentially related work creation:
 kasan_save_stack+0x1e/0x40
 __kasan_record_aux_stack+0x95/0xb0
 call_rcu+0x6a/0xa30
 kmemleak_free_percpu+0x9a/0x120
 free_percpu+0x2c/0xec0
 percpu_counter_destroy+0x11a/0x1c0
 wb_exit+0x82/0xb0
 cgwb_release_workfn+0x25d/0x3f0
 process_one_work+0xa17/0x16a0
 worker_thread+0x637/0x1260
 kthread+0x2ed/0x3a0
 ret_from_fork+0x22/0x30

The buggy address belongs to the object at ffff88800f25d440
 which belongs to the cache kmemleak_object of size 368
The buggy address is located 24 bytes inside of
 368-byte region [ffff88800f25d440, ffff88800f25d5b0)

The buggy address belongs to the physical page:
page:00000000af6a80f5 refcount:1 mapcount:0 mapping:0000000000000000 index:0xffffea00003e6580 pfn:0xf25c
head:00000000af6a80f5 order:1 compound_mapcount:0 compound_pincount:0
flags: 0x100000000010200(slab|head|node=0|zone=1)
raw: 0100000000010200 ffff888007c4f780 dead000000120012 0000000000000000
raw: ffffea00003e6580 dead000000000004 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff88800f25d300: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
 ffff88800f25d380: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff88800f25d400: fc fc fc fc fc fc fc fc fa fb fb fb fb fb fb fb
                                                    ^
 ffff88800f25d480: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
 ffff88800f25d500: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================