EXT4-fs warning (device loop0): dx_probe:832: inode #2: comm syz-executor.0: Unrecognised inode hash code 49
EXT4-fs warning (device loop0): dx_probe:965: inode #2: comm syz-executor.0: Corrupt directory, running e2fsck is recommended
==================================================================
BUG: KASAN: use-after-free in __ext4_check_dir_entry+0x700/0x880 fs/ext4/dir.c:85
Read of size 2 at addr ffff8881220ec003 by task syz-executor.0/366

CPU: 1 PID: 366 Comm: syz-executor.0 Not tainted 6.1.90-syzkaller-1151312-gbe8ff39d2e99 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
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_load2_noabort+0x14/0x20 mm/kasan/report_generic.c:349
 __ext4_check_dir_entry+0x700/0x880 fs/ext4/dir.c:85
 ext4_readdir+0x1386/0x3930 fs/ext4/dir.c:258
 iterate_dir+0x265/0x610
 __do_sys_getdents64 fs/readdir.c:369 [inline]
 __se_sys_getdents64+0x1c1/0x460 fs/readdir.c:354
 __x64_sys_getdents64+0x7b/0x90 fs/readdir.c:354
 x64_sys_call+0x5ae/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:218
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f518b87dd69
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:00007f518c5250c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000d9
RAX: ffffffffffffffda RBX: 00007f518b9abf80 RCX: 00007f518b87dd69
RDX: 0000000000000010 RSI: 0000000000000000 RDI: 0000000000000005
RBP: 00007f518b8ca49e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f518b9abf80 R15: 00007ffc7c173308
 </TASK>

The buggy address belongs to the physical page:
page:ffffea0004883b00 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x1220ec
flags: 0x4000000000000000(zone=1)
raw: 4000000000000000 ffffea0004883b48 ffff8881f703c768 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 366, tgid 365 (syz-executor.0), ts 41991073403, free_ts 41992446879
 set_page_owner include/linux/page_owner.h:33 [inline]
 post_alloc_hook+0x213/0x220 mm/page_alloc.c:2590
 prep_new_page+0x1b/0x110 mm/page_alloc.c:2597
 get_page_from_freelist+0x27ea/0x2870 mm/page_alloc.c:4425
 __alloc_pages+0x3a1/0x780 mm/page_alloc.c:5714
 __folio_alloc+0x15/0x40 mm/page_alloc.c:5746
 __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]
 wp_page_copy+0x23b/0x1690 mm/memory.c:3178
 do_wp_page+0xc5c/0xf30
 handle_pte_fault mm/memory.c:5145 [inline]
 __handle_mm_fault mm/memory.c:5269 [inline]
 handle_mm_fault+0x15e0/0x30e0 mm/memory.c:5409
 do_user_addr_fault arch/x86/mm/fault.c:1354 [inline]
 handle_page_fault arch/x86/mm/fault.c:1497 [inline]
 exc_page_fault+0x3b3/0x700 arch/x86/mm/fault.c:1553
 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:1498 [inline]
 free_pcp_prepare mm/page_alloc.c:1572 [inline]
 free_unref_page_prepare+0x83d/0x850 mm/page_alloc.c:3498
 free_unref_page_list+0xf1/0x7b0 mm/page_alloc.c:3646
 release_pages+0xf7f/0xfe0 mm/swap.c:1063
 free_pages_and_swap_cache+0x8a/0xa0 mm/swap_state.c:315
 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:2405
 do_mas_align_munmap+0xd05/0x1400 mm/mmap.c:2672
 do_mas_munmap+0x23e/0x2b0 mm/mmap.c:2730
 __vm_munmap+0x263/0x3a0 mm/mmap.c:3020
 __do_sys_munmap mm/mmap.c:3046 [inline]
 __se_sys_munmap mm/mmap.c:3042 [inline]
 __x64_sys_munmap+0x6b/0x80 mm/mmap.c:3042
 x64_sys_call+0x75/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:12
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2

Memory state around the buggy address:
 ffff8881220ebf00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff8881220ebf80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff8881220ec000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                   ^
 ffff8881220ec080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff8881220ec100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================
EXT4-fs error (device loop0): ext4_readdir:260: inode #2: block 255: comm syz-executor.0: path /root/syzkaller-testdir1198969710/syzkaller.bSFMwx/2/file0: bad entry in directory: directory entry overrun - offset=1023, inode=1528838656, rec_len=8224, size=1024 fake=0