[Android 6.1] KASAN: use-after-free Read in current_time

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 92668decd5e0 UPSTREAM: locking/rtmutex: Skip remove_waiter..
git tree: android14-6.1
console output: https://syzkaller.appspot.com/x/log.txt?x=16b84099580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6af0777879025b2
dashboard link: https://syzkaller.appspot.com/bug?extid=b4e7454086b441f8b04d
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11b84099580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11604232580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d489fb35aec8/disk-92668dec.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/33e640edad62/vmlinux-92668dec.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e0bb511e52c2/bzImage-92668dec.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b4e745...@syzkaller.appspotmail.com

==================================================================
BUG: KASAN: use-after-free in current_time+0xa8/0x2c0 fs/inode.c:2551
Read of size 8 at addr ffff88811641f428 by task syz.5.3354/10423

CPU: 1 PID: 10423 Comm: syz.5.3354 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/2026
Call Trace:
<TASK>
__dump_stack+0x21/0x24 lib/dump_stack.c:88
dump_stack_lvl+0x110/0x170 lib/dump_stack.c:106
print_address_description+0x71/0x200 mm/kasan/report.c:316
print_report+0x4a/0x60 mm/kasan/report.c:420
kasan_report+0x122/0x150 mm/kasan/report.c:524
__asan_report_load8_noabort+0x14/0x20 mm/kasan/report_generic.c:351
current_time+0xa8/0x2c0 fs/inode.c:2551
atime_needs_update+0x44a/0x810 fs/inode.c:2007
pick_link+0x496/0xe30 fs/namei.c:1788
step_into+0xc27/0xf00 fs/namei.c:1875
walk_component fs/namei.c:2011 [inline]
link_path_walk+0x744/0xeb0 fs/namei.c:2332
path_parentat fs/namei.c:2533 [inline]
__filename_parentat+0x22d/0x650 fs/namei.c:2557
filename_parentat fs/namei.c:2575 [inline]
do_unlinkat+0xeb/0x6c0 fs/namei.c:4368
__do_sys_unlinkat fs/namei.c:4440 [inline]
__se_sys_unlinkat fs/namei.c:4433 [inline]
__x64_sys_unlinkat+0xd8/0xf0 fs/namei.c:4433
x64_sys_call+0x79f/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:264
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fa1be19de99
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 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 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fa1bf050028 EFLAGS: 00000246 ORIG_RAX: 0000000000000107
RAX: ffffffffffffffda RBX: 00007fa1be425fa0 RCX: 00007fa1be19de99
RDX: 0000000000000000 RSI: 00002000000001c0 RDI: 0000000000000004
RBP: 00007fa1be233eaf R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fa1be426038 R14: 00007fa1be425fa0 R15: 00007fff261111e8
</TASK>

Allocated by task 10423:
kasan_save_stack mm/kasan/common.c:46 [inline]
kasan_set_track+0x4b/0x70 mm/kasan/common.c:53
kasan_save_alloc_info+0x1f/0x30 mm/kasan/generic.c:505
__kasan_slab_alloc+0x72/0x80 mm/kasan/common.c:334
kasan_slab_alloc include/linux/kasan.h:202 [inline]
slab_post_alloc_hook+0x4f/0x2d0 mm/slab.h:768
slab_alloc_node mm/slub.c:3382 [inline]
slab_alloc mm/slub.c:3392 [inline]
__kmem_cache_alloc_lru mm/slub.c:3399 [inline]
kmem_cache_alloc_lru+0x104/0x280 mm/slub.c:3415
alloc_inode_sb include/linux/fs.h:3263 [inline]
alloc_inode fs/inode.c:266 [inline]
new_inode_pseudo+0x8f/0x1f0 fs/inode.c:1074
new_inode+0x28/0x1e0 fs/inode.c:1102
bpf_get_inode kernel/bpf/inode.c:116 [inline]
bpf_symlink+0x65/0x270 kernel/bpf/inode.c:394
vfs_symlink+0x261/0x3f0 fs/namei.c:4478
do_symlinkat+0x24a/0x5d0 fs/namei.c:4507
__do_sys_symlinkat fs/namei.c:4524 [inline]
__se_sys_symlinkat fs/namei.c:4521 [inline]
__x64_sys_symlinkat+0x99/0xb0 fs/namei.c:4521
x64_sys_call+0x282/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:267
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2

Freed by task 10424:
kasan_save_stack mm/kasan/common.c:46 [inline]
kasan_set_track+0x4b/0x70 mm/kasan/common.c:53
kasan_save_free_info+0x2b/0x40 mm/kasan/generic.c:516
____kasan_slab_free+0x132/0x180 mm/kasan/common.c:242
__kasan_slab_free+0x11/0x20 mm/kasan/common.c:250
kasan_slab_free include/linux/kasan.h:178 [inline]
slab_free_hook mm/slub.c:1750 [inline]
slab_free_freelist_hook+0xc2/0x190 mm/slub.c:1776
slab_free mm/slub.c:3712 [inline]
kmem_cache_free+0x12d/0x300 mm/slub.c:3737
free_inode_nonrcu+0x1c/0x20 fs/inode.c:245
bpf_destroy_inode+0x14a/0x170 kernel/bpf/inode.c:621
destroy_inode fs/inode.c:314 [inline]
evict+0x7ac/0x8c0 fs/inode.c:724
iput_final fs/inode.c:1845 [inline]
iput+0x633/0x690 fs/inode.c:1871
do_unlinkat+0x380/0x6c0 fs/namei.c:4404
__do_sys_unlinkat fs/namei.c:4440 [inline]
__se_sys_unlinkat fs/namei.c:4433 [inline]
__x64_sys_unlinkat+0xd8/0xf0 fs/namei.c:4433
x64_sys_call+0x79f/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:264
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2

The buggy address belongs to the object at ffff88811641f400
which belongs to the cache inode_cache of size 704
The buggy address is located 40 bytes inside of
704-byte region [ffff88811641f400, ffff88811641f6c0)

The buggy address belongs to the physical page:
page:ffffea0004590700 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x11641c
head:ffffea0004590700 order:2 compound_mapcount:0 compound_pincount:0
flags: 0x4000000000010200(slab|head|zone=1)
raw: 4000000000010200 dead000000000100 dead000000000122 ffff8881001edc80
raw: 0000000000000000 0000000080130013 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 2, migratetype Reclaimable, gfp_mask 0xd20d0(__GFP_IO|__GFP_FS|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC|__GFP_RECLAIMABLE), pid 107, tgid 107 (udevd), ts 5903006214, free_ts 0
set_page_owner include/linux/page_owner.h:33 [inline]
post_alloc_hook+0x1f5/0x210 mm/page_alloc.c:2672
prep_new_page+0x1c/0x110 mm/page_alloc.c:2679
get_page_from_freelist+0x2ca9/0x2d20 mm/page_alloc.c:4586
__alloc_pages+0x1fa/0x610 mm/page_alloc.c:5930
alloc_slab_page+0x6e/0xf0 include/linux/gfp.h:-1
allocate_slab mm/slub.c:1967 [inline]
new_slab+0x98/0x3e0 mm/slub.c:2020
___slab_alloc+0x70f/0xb70 mm/slub.c:3177
__slab_alloc+0x5e/0xa0 mm/slub.c:3263
slab_alloc_node mm/slub.c:3348 [inline]
slab_alloc mm/slub.c:3392 [inline]
__kmem_cache_alloc_lru mm/slub.c:3399 [inline]
kmem_cache_alloc_lru+0x144/0x280 mm/slub.c:3415
alloc_inode_sb include/linux/fs.h:3263 [inline]
alloc_inode fs/inode.c:266 [inline]
iget_locked+0x1dc/0x840 fs/inode.c:1384
kernfs_get_inode+0x4b/0x6e0 fs/kernfs/inode.c:254
kernfs_iop_lookup+0x20f/0x310 fs/kernfs/dir.c:1189
__lookup_slow+0x2d5/0x410 fs/namei.c:1697
lookup_slow+0x57/0x70 fs/namei.c:1714
walk_component+0x2f5/0x430 fs/namei.c:2005
lookup_last fs/namei.c:2462 [inline]
path_lookupat+0x155/0x430 fs/namei.c:2486
page_owner free stack trace missing

Memory state around the buggy address:
ffff88811641f300: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff88811641f380: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
>ffff88811641f400: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff88811641f480: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff88811641f500: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup