EXT4-fs warning (device loop2): dx_probe:833: inode #2: comm syz.2.17: Unrecognised inode hash code 4
EXT4-fs warning (device loop2): dx_probe:966: inode #2: comm syz.2.17: Corrupt directory, running e2fsck is recommended
==================================================================
BUG: KASAN: use-after-free in __ext4_check_dir_entry+0x7c2/0x970 fs/ext4/dir.c:85
Read of size 2 at addr ffff88812ed99003 by task syz.2.17/373

CPU: 1 PID: 373 Comm: syz.2.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
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_load2_noabort+0x14/0x20 mm/kasan/report_generic.c:349
 __ext4_check_dir_entry+0x7c2/0x970 fs/ext4/dir.c:85
 ext4_readdir+0x1315/0x3e10 fs/ext4/dir.c:261
 iterate_dir+0x271/0x610 fs/readdir.c:-1
 __do_sys_getdents64 fs/readdir.c:369 [inline]
 __se_sys_getdents64+0xf2/0x250 fs/readdir.c:354
 __x64_sys_getdents64+0x7b/0x90 fs/readdir.c:354
 x64_sys_call+0x15c/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:218
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f49c7d9acb9
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:00007ffdb9abeaa8 EFLAGS: 00000246 ORIG_RAX: 00000000000000d9
RAX: ffffffffffffffda RBX: 00007f49c8015fa0 RCX: 00007f49c7d9acb9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000006
RBP: 00007f49c7e08bf7 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f49c8015fac R14: 00007f49c8015fa0 R15: 00007f49c8015fa0
 </TASK>

The buggy address belongs to the physical page:
page:ffffea0004bb6640 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x12ed99
flags: 0x4000000000000000(zone=1)
raw: 4000000000000000 ffffea0004bb6688 ffff8881f703c868 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 373, tgid 373 (syz.2.17), ts 30822434765, free_ts 30824271870
 set_page_owner include/linux/page_owner.h:33 [inline]
 post_alloc_hook+0x1f5/0x210 mm/page_alloc.c:2643
 prep_new_page+0x1c/0x110 mm/page_alloc.c:2650
 get_page_from_freelist+0x2d12/0x2d80 mm/page_alloc.c:4554
 __alloc_pages+0x1d9/0x480 mm/page_alloc.c:5868
 __folio_alloc+0x12/0x40 mm/page_alloc.c:5900
 __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+0x27d/0x15a0 mm/memory.c:3204
 do_wp_page+0x9f2/0xfc0 mm/memory.c:-1
 handle_pte_fault mm/memory.c:5189 [inline]
 __handle_mm_fault mm/memory.c:5313 [inline]
 handle_mm_fault+0x1124/0x26c0 mm/memory.c:5453
 do_user_addr_fault+0x905/0x1050 arch/x86/mm/fault.c:1323
 handle_page_fault arch/x86/mm/fault.c:1466 [inline]
 exc_page_fault+0x51/0xb0 arch/x86/mm/fault.c:1522
 asm_exc_page_fault+0x27/0x30 arch/x86/include/asm/idtentry.h:608
page last free stack trace:
 reset_page_owner include/linux/page_owner.h:26 [inline]
 free_pages_prepare mm/page_alloc.c:1551 [inline]
 free_pcp_prepare mm/page_alloc.c:1625 [inline]
 free_unref_page_prepare+0x742/0x750 mm/page_alloc.c:3589
 free_unref_page_list+0x117/0x8c0 mm/page_alloc.c:3740
 release_pages+0xaf2/0xb50 mm/swap.c:1048
 free_pages_and_swap_cache+0x86/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+0x1aa/0x370 mm/mmu_gather.c:361
 unmap_region+0x2b7/0x320 mm/mmap.c:2419
 do_mas_align_munmap+0xbed/0x1320 mm/mmap.c:2693
 do_mas_munmap+0x241/0x2b0 mm/mmap.c:2751
 __vm_munmap+0x1bd/0x330 mm/mmap.c:3050
 __do_sys_munmap mm/mmap.c:3076 [inline]
 __se_sys_munmap mm/mmap.c:3072 [inline]
 __x64_sys_munmap+0x6b/0x80 mm/mmap.c:3072
 x64_sys_call+0x8a/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:12
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2

Memory state around the buggy address:
 ffff88812ed98f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff88812ed98f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff88812ed99000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                   ^
 ffff88812ed99080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff88812ed99100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================
EXT4-fs error (device loop2): ext4_readdir:263: inode #2: block 255: comm syz.2.17: path (unknown): bad entry in directory: rec_len is smaller than minimal - offset=1023, inode=0, rec_len=0, size=1024 fake=0