==================================================================
BUG: KASAN: use-after-free in keyring_compare_object+0x1cb/0x220 security/keys/keyring.c:314
Read of size 8 at addr ffff88809a76d630 by task syz-executor.2/19274

CPU: 1 PID: 19274 Comm: syz-executor.2 Not tainted 5.3.0-rc3+ #102
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x172/0x1f0 lib/dump_stack.c:113
 print_address_description.cold+0xd4/0x306 mm/kasan/report.c:351
 __kasan_report.cold+0x1b/0x36 mm/kasan/report.c:482
 kasan_report+0x12/0x17 mm/kasan/common.c:612
 __asan_report_load8_noabort+0x14/0x20 mm/kasan/generic_report.c:132
 keyring_compare_object+0x1cb/0x220 security/keys/keyring.c:314
 assoc_array_find+0x14b/0x1f0 lib/assoc_array.c:331
 search_keyring security/keys/keyring.c:655 [inline]
 search_nested_keyrings+0xb15/0xea0 security/keys/keyring.c:722
 keyring_search_rcu+0x1b4/0x290 security/keys/keyring.c:926
 search_cred_keyrings_rcu+0x17d/0x2e0 security/keys/process_keys.c:480
 search_process_keyrings_rcu+0x1d/0x320 security/keys/process_keys.c:544
 request_key_and_link+0x264/0x12b0 security/keys/request_key.c:602
 __do_sys_request_key security/keys/keyctl.c:223 [inline]
 __se_sys_request_key security/keys/keyctl.c:168 [inline]
 __x64_sys_request_key+0x285/0x430 security/keys/keyctl.c:168
 do_syscall_64+0xfd/0x6a0 arch/x86/entry/common.c:296
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x459829
Code: fd b7 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 cb b7 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f4b08d27c78 EFLAGS: 00000246 ORIG_RAX: 00000000000000f9
RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 0000000000459829
RDX: 0000000020000340 RSI: 0000000020000300 RDI: 00000000200002c0
RBP: 000000000075bf20 R08: 0000000000000000 R09: 0000000000000000
R10: fffffffffffffffe R11: 0000000000000246 R12: 00007f4b08d286d4
R13: 00000000004c6dba R14: 00000000004dc1a0 R15: 00000000ffffffff

Allocated by task 16508:
 save_stack+0x23/0x90 mm/kasan/common.c:69
 set_track mm/kasan/common.c:77 [inline]
 __kasan_kmalloc mm/kasan/common.c:487 [inline]
 __kasan_kmalloc.constprop.0+0xcf/0xe0 mm/kasan/common.c:460
 kasan_slab_alloc+0xf/0x20 mm/kasan/common.c:495
 slab_post_alloc_hook mm/slab.h:520 [inline]
 slab_alloc mm/slab.c:3319 [inline]
 kmem_cache_alloc+0x121/0x710 mm/slab.c:3483
 kmem_cache_zalloc include/linux/slab.h:738 [inline]
 key_alloc+0x426/0x1110 security/keys/key.c:276
 key_create_or_update+0x651/0xbe0 security/keys/key.c:924
 __do_sys_add_key security/keys/keyctl.c:132 [inline]
 __se_sys_add_key security/keys/keyctl.c:72 [inline]
 __x64_sys_add_key+0x2bd/0x4f0 security/keys/keyctl.c:72
 do_syscall_64+0xfd/0x6a0 arch/x86/entry/common.c:296
 entry_SYSCALL_64_after_hwframe+0x49/0xbe

Freed by task 2851:
 save_stack+0x23/0x90 mm/kasan/common.c:69
 set_track mm/kasan/common.c:77 [inline]
 __kasan_slab_free+0x102/0x150 mm/kasan/common.c:449
 kasan_slab_free+0xe/0x10 mm/kasan/common.c:457
 __cache_free mm/slab.c:3425 [inline]
 kmem_cache_free+0x86/0x320 mm/slab.c:3693
 key_gc_unused_keys.constprop.0+0x192/0x5b0 security/keys/gc.c:157
 key_garbage_collector+0x3f3/0x940 security/keys/gc.c:292
 process_one_work+0x9af/0x1740 kernel/workqueue.c:2269
 worker_thread+0x98/0xe40 kernel/workqueue.c:2415
 kthread+0x361/0x430 kernel/kthread.c:255
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:352

The buggy address belongs to the object at ffff88809a76d540
 which belongs to the cache key_jar of size 304
The buggy address is located 240 bytes inside of
 304-byte region [ffff88809a76d540, ffff88809a76d670)
The buggy address belongs to the page:
page:ffffea000269db40 refcount:1 mapcount:0 mapping:ffff88821bc461c0 index:0x0
flags: 0x1fffc0000000200(slab)
raw: 01fffc0000000200 ffffea00028880c8 ffffea0002a02608 ffff88821bc461c0
raw: 0000000000000000 ffff88809a76d0c0 000000010000000a 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff88809a76d500: fc fc fc fc fc fc fc fc fb fb fb fb fb fb fb fb
 ffff88809a76d580: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff88809a76d600: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fc fc
                                     ^
 ffff88809a76d680: fc fc fc fc fc fc fc fc fb fb fb fb fb fb fb fb
 ffff88809a76d700: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================