==================================================================
BUG: KASAN: slab-use-after-free in __mutex_lock+0x801/0x1350
Read of size 8 at addr ffff88802a3840a0 by task khidpd_16bf5505/6517

CPU: 0 UID: 0 PID: 6517 Comm: khidpd_16bf5505 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250
 print_report+0xca/0x240
 kasan_report+0x118/0x150
 __mutex_lock+0x801/0x1350
 l2cap_unregister_user+0x6a/0x1b0
 hidp_session_thread+0x3c9/0x410
 kthread+0x711/0x8a0
 ret_from_fork+0x3fc/0x770
 ret_from_fork_asm+0x1a/0x30
 </TASK>

Allocated by task 5845:
 kasan_save_track+0x3e/0x80
 __kasan_kmalloc+0x93/0xb0
 __kmalloc_noprof+0x27a/0x4f0
 hci_alloc_dev_priv+0x28/0x2060
 vhci_create_device+0x120/0x6e0
 vhci_write+0x3ce/0x4a0
 vfs_write+0x5c9/0xb30
 ksys_write+0x145/0x250
 do_syscall_64+0xfa/0x3b0
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Freed by task 5845:
 kasan_save_track+0x3e/0x80
 kasan_save_free_info+0x46/0x50
 __kasan_slab_free+0x5b/0x80
 kfree+0x18e/0x440
 bt_host_release+0x82/0x90
 device_release+0x9c/0x1c0
 kobject_put+0x22b/0x480
 vhci_release+0x88/0xd0
 __fput+0x44c/0xa70
 task_work_run+0x1d4/0x260
 do_exit+0x6b5/0x2300
 do_group_exit+0x21c/0x2d0
 __x64_sys_exit_group+0x3f/0x40
 x64_sys_call+0x21f7/0x2200
 do_syscall_64+0xfa/0x3b0
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Last potentially related work creation:
 kasan_save_stack+0x3e/0x60
 kasan_record_aux_stack+0xbd/0xd0
 insert_work+0x3d/0x330
 __queue_work+0xcd2/0xfb0
 queue_work_on+0x181/0x270
 l2cap_chan_send+0x1110/0x2790
 l2cap_sock_sendmsg+0x32e/0x4a0
 __sock_sendmsg+0x21c/0x270
 ____sys_sendmsg+0x52d/0x830
 ___sys_sendmsg+0x21f/0x2a0
 __sys_sendmmsg+0x227/0x430
 __x64_sys_sendmmsg+0xa0/0xc0
 do_syscall_64+0xfa/0x3b0
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Second to last potentially related work creation:
 kasan_save_stack+0x3e/0x60
 kasan_record_aux_stack+0xbd/0xd0
 insert_work+0x3d/0x330
 __queue_work+0xcd2/0xfb0
 queue_work_on+0x181/0x270
 l2cap_chan_send+0x1110/0x2790
 l2cap_sock_sendmsg+0x32e/0x4a0
 __sock_sendmsg+0x21c/0x270
 ____sys_sendmsg+0x52d/0x830
 ___sys_sendmsg+0x21f/0x2a0
 __sys_sendmmsg+0x227/0x430
 __x64_sys_sendmmsg+0xa0/0xc0
 do_syscall_64+0xfa/0x3b0
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

The buggy address belongs to the object at ffff88802a384000
 which belongs to the cache kmalloc-8k of size 8192
The buggy address is located 160 bytes inside of
 freed 8192-byte region [ffff88802a384000, ffff88802a386000)

The buggy address belongs to the physical page:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x2a380
head: order:3 mapcount:0 entire_mapcount:0 nr_pages_mapped:0 pincount:0
flags: 0xfff00000000040(head|node=0|zone=1|lastcpupid=0x7ff)
page_type: f5(slab)
raw: 00fff00000000040 ffff88801a442280 dead000000000100 dead000000000122
raw: 0000000000000000 0000000000020002 00000000f5000000 0000000000000000
head: 00fff00000000040 ffff88801a442280 dead000000000100 dead000000000122
head: 0000000000000000 0000000000020002 00000000f5000000 0000000000000000
head: 00fff00000000003 ffffea0000a8e001 00000000ffffffff 00000000ffffffff
head: ffffffffffffffff 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 0xd2040(__GFP_IO|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC), pid 5671, tgid 5671 (init), ts 25167516936, free_ts 0
 post_alloc_hook+0x240/0x2a0
 get_page_from_freelist+0x21e4/0x22c0
 __alloc_frozen_pages_noprof+0x181/0x370
 alloc_pages_mpol+0x232/0x4a0
 allocate_slab+0x8a/0x370
 ___slab_alloc+0xbeb/0x1410
 __kmalloc_cache_noprof+0x296/0x3d0
 tomoyo_init_log+0x111f/0x1f70
 tomoyo_supervisor+0x340/0x1480
 tomoyo_env_perm+0x149/0x1e0
 tomoyo_find_next_domain+0x15cf/0x1aa0
 tomoyo_bprm_check_security+0x11c/0x180
 security_bprm_check+0x89/0x270
 bprm_execve+0x8ee/0x1450
 do_execveat_common+0x510/0x6a0
 __x64_sys_execve+0x94/0xb0
page_owner free stack trace missing

Memory state around the buggy address:
 ffff88802a383f80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
 ffff88802a384000: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff88802a384080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
                               ^
 ffff88802a384100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
 ffff88802a384180: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================
