==================================================================
BUG: KASAN: use-after-free in __lock_acquire+0x2cb4/0x3ff0 kernel/locking/lockdep.c:3295
Read of size 8 at addr ffff8880afc74d20 by task kworker/1:3/9357

CPU: 1 PID: 9357 Comm: kworker/1:3 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events sco_sock_timeout
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_load8_noabort+0x88/0x90 mm/kasan/report.c:433
 __lock_acquire+0x2cb4/0x3ff0 kernel/locking/lockdep.c:3295
 lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3908
 __raw_spin_lock include/linux/spinlock_api_smp.h:142 [inline]
 _raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:144
 spin_lock include/linux/spinlock.h:329 [inline]
 sco_sock_timeout+0x7b/0x1b0 net/bluetooth/sco.c:95
 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 8137:
 __do_kmalloc_node mm/slab.c:3689 [inline]
 __kmalloc_node+0x4c/0x70 mm/slab.c:3696
 kmalloc_node include/linux/slab.h:557 [inline]
 kvmalloc_node+0x61/0xf0 mm/util.c:423
 kvmalloc include/linux/mm.h:577 [inline]
 kvmalloc_array include/linux/mm.h:595 [inline]
 alloc_fdtable+0xcd/0x280 fs/file.c:115
 dup_fd+0x6a2/0xbf0 fs/file.c:310
 copy_files kernel/fork.c:1391 [inline]
 copy_process.part.0+0x1e75/0x8260 kernel/fork.c:1901
 copy_process kernel/fork.c:1710 [inline]
 _do_fork+0x22f/0xf30 kernel/fork.c:2219
 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe

Freed by task 16815:
 __cache_free mm/slab.c:3503 [inline]
 kfree+0xcc/0x210 mm/slab.c:3822
 kvfree+0x59/0x60 mm/util.c:452
 __free_fdtable fs/file.c:31 [inline]
 put_files_struct fs/file.c:420 [inline]
 put_files_struct+0x267/0x350 fs/file.c:413
 exit_files+0x7e/0xa0 fs/file.c:445
 do_exit+0xbb9/0x2be0 kernel/exit.c:865
 do_group_exit+0x125/0x310 kernel/exit.c:967
 get_signal+0x3f2/0x1f70 kernel/signal.c:2589
 do_signal+0x8f/0x1670 arch/x86/kernel/signal.c:799
 exit_to_usermode_loop+0x204/0x2a0 arch/x86/entry/common.c:163
 prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
 syscall_return_slowpath arch/x86/entry/common.c:271 [inline]
 do_syscall_64+0x538/0x620 arch/x86/entry/common.c:296
 entry_SYSCALL_64_after_hwframe+0x49/0xbe

The buggy address belongs to the object at ffff8880afc74c80
 which belongs to the cache kmalloc-2048 of size 2048
The buggy address is located 160 bytes inside of
 2048-byte region [ffff8880afc74c80, ffff8880afc75480)
The buggy address belongs to the page:
page:ffffea0002bf1d00 count:1 mapcount:0 mapping:ffff88813bff0c40 index:0xffff8880afc75500 compound_mapcount: 0
flags: 0xfff00000008100(slab|head)
raw: 00fff00000008100 ffffea0001678b88 ffffea0001db8188 ffff88813bff0c40
raw: ffff8880afc75500 ffff8880afc74400 0000000100000002 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
uinput: write device info first
 ffff8880afc74c00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
 ffff8880afc74c80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff8880afc74d00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
                               ^
 ffff8880afc74d80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
 ffff8880afc74e00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================