[Android 5.15] KASAN: use-after-free Read in atime_needs_update

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 8969ee93a483 Merge android13-5.15 into android13-5.15-lts
git tree: android13-5.15-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=16b05886580000
kernel config: https://syzkaller.appspot.com/x/.config?x=3ef8af16142b9dd4
dashboard link: https://syzkaller.appspot.com/bug?extid=8d57d64702ce53fbe343
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16ab4da6580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13be0ef2580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d686db73bf84/disk-8969ee93.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6253ebf315ec/vmlinux-8969ee93.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a673b5918e79/bzImage-8969ee93.xz

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

==================================================================
BUG: KASAN: use-after-free in atime_needs_update+0x754/0x810 fs/inode.c:1922
Read of size 4 at addr ffff88813174a5dc by task syz.1.1270/4163

CPU: 1 PID: 4163 Comm: syz.1.1270 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Call Trace:
<TASK>
__dump_stack+0x21/0x30 lib/dump_stack.c:88
dump_stack_lvl+0x110/0x170 lib/dump_stack.c:106
print_address_description+0x7f/0x2c0 mm/kasan/report.c:248
__kasan_report mm/kasan/report.c:427 [inline]
kasan_report+0xf1/0x140 mm/kasan/report.c:444
__asan_report_load4_noabort+0x14/0x20 mm/kasan/report_generic.c:308
atime_needs_update+0x754/0x810 fs/inode.c:1922
pick_link+0x4b9/0xe00 fs/namei.c:1762
step_into+0xafc/0xd20 fs/namei.c:1840
walk_component+0x26a/0x460 fs/namei.c:1990
link_path_walk+0x665/0xd60 fs/namei.c:-1
path_parentat fs/namei.c:2510 [inline]
__filename_parentat+0x252/0x690 fs/namei.c:2534
filename_parentat fs/namei.c:2552 [inline]
do_unlinkat+0xeb/0x6d0 fs/namei.c:4327
__do_sys_unlinkat fs/namei.c:4399 [inline]
__se_sys_unlinkat fs/namei.c:4392 [inline]
__x64_sys_unlinkat+0xd8/0xf0 fs/namei.c:4392
x64_sys_call+0x4c0/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:264
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fd663f8fe59
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:00007fd663df2028 EFLAGS: 00000246 ORIG_RAX: 0000000000000107
RAX: ffffffffffffffda RBX: 00007fd664208fa0 RCX: 00007fd663f8fe59
RDX: 0000000000000000 RSI: 00002000000001c0 RDI: 0000000000000004
RBP: 00007fd664025d6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fd664209038 R14: 00007fd664208fa0 R15: 00007ffcd9381078
</TASK>

Allocated by task 4163:
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track mm/kasan/common.c:45 [inline]
set_alloc_info mm/kasan/common.c:433 [inline]
__kasan_slab_alloc+0xbd/0xf0 mm/kasan/common.c:466
kasan_slab_alloc include/linux/kasan.h:217 [inline]
slab_post_alloc_hook+0x4f/0x2b0 mm/slab.h:550
slab_alloc_node mm/slub.c:3245 [inline]
slab_alloc mm/slub.c:3255 [inline]
kmem_cache_alloc+0xf7/0x260 mm/slub.c:3260
alloc_inode fs/inode.c:266 [inline]
new_inode_pseudo+0x7a/0x210 fs/inode.c:1011
new_inode+0x28/0x1e0 fs/inode.c:1040
bpf_get_inode kernel/bpf/inode.c:116 [inline]
bpf_symlink+0x65/0x270 kernel/bpf/inode.c:394
vfs_symlink+0x29e/0x470 fs/namei.c:4437
do_symlinkat+0x124/0x5a0 fs/namei.c:4466
__do_sys_symlinkat fs/namei.c:4483 [inline]
__se_sys_symlinkat fs/namei.c:4480 [inline]
__x64_sys_symlinkat+0x99/0xb0 fs/namei.c:4480
x64_sys_call+0x74b/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:267
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0

Freed by task 4164:
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track+0x4a/0x70 mm/kasan/common.c:45
kasan_set_free_info+0x23/0x40 mm/kasan/generic.c:370
____kasan_slab_free+0x125/0x160 mm/kasan/common.c:365
__kasan_slab_free+0x11/0x20 mm/kasan/common.c:373
kasan_slab_free include/linux/kasan.h:193 [inline]
slab_free_hook mm/slub.c:1728 [inline]
slab_free_freelist_hook+0xc2/0x190 mm/slub.c:1754
slab_free mm/slub.c:3526 [inline]
kmem_cache_free+0x100/0x320 mm/slub.c:3544
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+0x7b4/0x8d0 fs/inode.c:665
iput_final fs/inode.c:1779 [inline]
iput+0x635/0x7c0 fs/inode.c:1805
do_unlinkat+0x380/0x6d0 fs/namei.c:4363
__do_sys_unlinkat fs/namei.c:4399 [inline]
__se_sys_unlinkat fs/namei.c:4392 [inline]
__x64_sys_unlinkat+0xd8/0xf0 fs/namei.c:4392
x64_sys_call+0x4c0/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:264
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0

The buggy address belongs to the object at ffff88813174a5d0
which belongs to the cache inode_cache of size 752
The buggy address is located 12 bytes inside of
752-byte region [ffff88813174a5d0, ffff88813174a8c0)
The buggy address belongs to the page:
page:ffffea0004c5d200 refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff88813174ba70 pfn:0x131748
head:ffffea0004c5d200 order:2 compound_mapcount:0 compound_pincount:0
flags: 0x4000000000010200(slab|head|zone=1)
raw: 4000000000010200 ffffea0004c5dc00 0000000700000007 ffff8881001c5380
raw: ffff88813174ba70 000000008012000b 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 0x1d20d0(__GFP_IO|__GFP_FS|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC|__GFP_HARDWALL|__GFP_RECLAIMABLE), pid 1221, ts 33087034573, free_ts 0
set_page_owner include/linux/page_owner.h:33 [inline]
post_alloc_hook+0x192/0x1b0 mm/page_alloc.c:2605
prep_new_page+0x1c/0x110 mm/page_alloc.c:2611
get_page_from_freelist+0x2d3a/0x2dc0 mm/page_alloc.c:4485
__alloc_pages+0x1a2/0x460 mm/page_alloc.c:5822
alloc_slab_page mm/slub.c:-1 [inline]
allocate_slab mm/slub.c:1937 [inline]
new_slab+0xa1/0x4d0 mm/slub.c:2000
___slab_alloc+0x381/0x810 mm/slub.c:3033
__slab_alloc+0x49/0x90 mm/slub.c:3120
slab_alloc_node mm/slub.c:3211 [inline]
slab_alloc mm/slub.c:3255 [inline]
kmem_cache_alloc+0x138/0x260 mm/slub.c:3260
alloc_inode fs/inode.c:266 [inline]
new_inode_pseudo+0x7a/0x210 fs/inode.c:1011
new_inode+0x28/0x1e0 fs/inode.c:1040
bpf_get_inode kernel/bpf/inode.c:116 [inline]
bpf_symlink+0x65/0x270 kernel/bpf/inode.c:394
vfs_symlink+0x29e/0x470 fs/namei.c:4437
do_symlinkat+0x124/0x5a0 fs/namei.c:4466
__do_sys_symlinkat fs/namei.c:4483 [inline]
__se_sys_symlinkat fs/namei.c:4480 [inline]
__x64_sys_symlinkat+0x99/0xb0 fs/namei.c:4480
x64_sys_call+0x74b/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:267
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
page_owner free stack trace missing

Memory state around the buggy address:
ffff88813174a480: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff88813174a500: fb fb fb fb fb fb fb fb fb fb fc fc fc fc fc fc
>ffff88813174a580: fc fc fc fc fc fc fc fc fc fc fa fb fb fb fb fb
^
ffff88813174a600: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff88813174a680: 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