==================================================================
BUG: KASAN: use-after-free in ext4_search_dir+0xf7/0x1b0 fs/ext4/namei.c:1516
Read of size 1 at addr ffff888120aa96e3 by task syz-executor.0/355

CPU: 1 PID: 355 Comm: syz-executor.0 Not tainted 5.10.225-syzkaller-1003235-g8d23314f588a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack_lvl+0x1e2/0x24b lib/dump_stack.c:118
 print_address_description+0x81/0x3b0 mm/kasan/report.c:248
 __kasan_report mm/kasan/report.c:435 [inline]
 kasan_report+0x179/0x1c0 mm/kasan/report.c:452
 __asan_report_load1_noabort+0x14/0x20 mm/kasan/report_generic.c:306
 ext4_search_dir+0xf7/0x1b0 fs/ext4/namei.c:1516
 ext4_find_inline_entry+0x4b6/0x5e0 fs/ext4/inline.c:1700
 __ext4_find_entry+0x2b0/0x1990 fs/ext4/namei.c:1589
 ext4_lookup_entry fs/ext4/namei.c:1744 [inline]
 ext4_lookup+0x3c6/0xaa0 fs/ext4/namei.c:1812
 lookup_open fs/namei.c:3226 [inline]
 open_last_lookups fs/namei.c:3317 [inline]
 path_openat+0x11ab/0x3000 fs/namei.c:3506
 do_filp_open+0x21c/0x460 fs/namei.c:3536
 do_sys_openat2+0x13f/0x710 fs/open.c:1217
 do_sys_open fs/open.c:1233 [inline]
 __do_sys_openat fs/open.c:1249 [inline]
 __se_sys_openat fs/open.c:1244 [inline]
 __x64_sys_openat+0x243/0x290 fs/open.c:1244
 do_syscall_64+0x34/0x70
 entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f0428b16e69
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 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 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f04286980c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f0428c44f80 RCX: 00007f0428b16e69
RDX: 000000000000275a RSI: 0000000020000280 RDI: ffffffffffffff9c
RBP: 00007f0428b6347a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f0428c44f80 R15: 00007ffc14f3b4b8

The buggy address belongs to the page:
page:ffffea000482aa40 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x120aa9
flags: 0x4000000000000000()
raw: 4000000000000000 ffffea000482aa88 ffffea000482aa08 0000000000000000
raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner info is not present (never set?)

Memory state around the buggy address:
 ffff888120aa9580: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff888120aa9600: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff888120aa9680: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                                                       ^
 ffff888120aa9700: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff888120aa9780: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================
EXT4-fs error (device loop0): ext4_find_dest_de:2077: inode #12: block 5: comm syz-executor.0: bad entry in directory: rec_len % 4 != 0 - offset=0, inode=1375716473, rec_len=40042, size=56 fake=0