==================================================================
BUG: KASAN: use-after-free in ext4_search_dir+0xf7/0x1b0 fs/ext4/namei.c:1539
Read of size 1 at addr ffff888121330d23 by task syz-executor157/300

CPU: 1 PID: 300 Comm: syz-executor157 Not tainted 6.1.43-syzkaller-00018-gb496cc311544 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
 print_address_description mm/kasan/report.c:316 [inline]
 print_report+0x158/0x4e0 mm/kasan/report.c:427
 kasan_report+0x13c/0x170 mm/kasan/report.c:531
 __asan_report_load1_noabort+0x14/0x20 mm/kasan/report_generic.c:348
 ext4_search_dir+0xf7/0x1b0 fs/ext4/namei.c:1539
 ext4_find_inline_entry+0x4b6/0x5e0 fs/ext4/inline.c:1722
 __ext4_find_entry+0x2b0/0x1af0 fs/ext4/namei.c:1612
 ext4_lookup_entry fs/ext4/namei.c:1767 [inline]
 ext4_lookup+0x176/0x740 fs/ext4/namei.c:1835
 __lookup_hash+0x143/0x290 fs/namei.c:1601
 filename_create+0x288/0x520 fs/namei.c:3808
 do_mkdirat+0xbd/0x450 fs/namei.c:4051
 __do_sys_mkdirat fs/namei.c:4076 [inline]
 __se_sys_mkdirat fs/namei.c:4074 [inline]
 __x64_sys_mkdirat+0x89/0xa0 fs/namei.c:4074
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f75dc7ed529
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 18 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe20e076d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007f75dc83608d RCX: 00007f75dc7ed529
RDX: 0000000000000000 RSI: 0000000020000040 RDI: 00000000ffffff9c
RBP: 0030656c69662f2e R08: 00000000000014ef R09: 0000000020001580
R10: 00000000000014f3 R11: 0000000000000246 R12: 0000000000000001
R13: 0000000000000000 R14: 431bde82d7b634db R15: 00007ffe20e07740
 </TASK>

The buggy address belongs to the physical page:
page:ffffea000484cc00 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x121330
flags: 0x4000000000000000(zone=1)
raw: 4000000000000000 ffffea000484cc48 ffffea000484cbc8 0000000000000000
raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as freed
page last allocated via order 0, migratetype Movable, gfp_mask 0x8140dca(GFP_HIGHUSER_MOVABLE|__GFP_COMP|__GFP_ZERO|__GFP_CMA), pid 281, tgid 281 (sshd), ts 20086708573, free_ts 20103879166
 set_page_owner include/linux/page_owner.h:33 [inline]
 post_alloc_hook+0x213/0x220 mm/page_alloc.c:2586
 prep_new_page+0x1b/0x110 mm/page_alloc.c:2593
 get_page_from_freelist+0x2878/0x2910 mm/page_alloc.c:4410
 __alloc_pages+0x3a1/0x780 mm/page_alloc.c:5698
 __folio_alloc+0x15/0x40 mm/page_alloc.c:5730
 __folio_alloc_node include/linux/gfp.h:245 [inline]
 folio_alloc include/linux/gfp.h:274 [inline]
 alloc_page_vma include/linux/gfp.h:283 [inline]
 do_anonymous_page mm/memory.c:4176 [inline]
 handle_pte_fault mm/memory.c:5055 [inline]
 __handle_mm_fault mm/memory.c:5199 [inline]
 handle_mm_fault+0x1fb0/0x2f40 mm/memory.c:5339
 do_user_addr_fault arch/x86/mm/fault.c:1363 [inline]
 handle_page_fault arch/x86/mm/fault.c:1504 [inline]
 exc_page_fault+0x3a6/0x6e0 arch/x86/mm/fault.c:1560
 asm_exc_page_fault+0x27/0x30 arch/x86/include/asm/idtentry.h:570
page last free stack trace:
 reset_page_owner include/linux/page_owner.h:26 [inline]
 free_pages_prepare mm/page_alloc.c:1494 [inline]
 free_pcp_prepare mm/page_alloc.c:1568 [inline]
 free_unref_page_prepare+0x83d/0x850 mm/page_alloc.c:3500
 free_unref_page_list+0xf6/0x6c0 mm/page_alloc.c:3649
 release_pages+0xf7f/0xfe0 mm/swap.c:1055
 free_pages_and_swap_cache+0x8a/0xa0 mm/swap_state.c:314
 tlb_batch_pages_flush mm/mmu_gather.c:59 [inline]
 tlb_flush_mmu_free mm/mmu_gather.c:254 [inline]
 tlb_flush_mmu mm/mmu_gather.c:261 [inline]
 tlb_finish_mmu+0x1e0/0x3f0 mm/mmu_gather.c:361
 unmap_region+0x2c1/0x310 mm/mmap.c:2389
 do_mas_align_munmap+0xd05/0x1400 mm/mmap.c:2654
 do_mas_munmap+0x23e/0x2b0 mm/mmap.c:2712
 __vm_munmap+0x263/0x3a0 mm/mmap.c:3002
 __do_sys_munmap mm/mmap.c:3028 [inline]
 __se_sys_munmap mm/mmap.c:3024 [inline]
 __x64_sys_munmap+0x6b/0x80 mm/mmap.c:3024
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd

Memory state around the buggy address:
 ffff888121330c00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff888121330c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff888121330d00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                               ^
 ffff888121330d80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff888121330e00: 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:2108: inode #12: block 7: comm syz-executor157: bad entry in directory: rec_len % 4 != 0 - offset=0, inode=3089191003, rec_len=43069, size=56 fake=0