EXT4-fs warning (device loop2): dx_probe:806: inode #2: comm syz.2.18: Unrecognised inode hash code 4
EXT4-fs warning (device loop2): dx_probe:946: inode #2: comm syz.2.18: 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 ffff88812bf17003 by task syz.2.18/501

CPU: 0 PID: 501 Comm: syz.2.18 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/14/2025
Call Trace:
 __dump_stack+0x21/0x24 lib/dump_stack.c:77
 dump_stack_lvl+0x169/0x1d8 lib/dump_stack.c:118
 print_address_description+0x7f/0x2c0 mm/kasan/report.c:248
 __kasan_report mm/kasan/report.c:435 [inline]
 kasan_report+0xe2/0x130 mm/kasan/report.c:452
 __asan_report_load2_noabort+0x14/0x20 mm/kasan/report_generic.c:307
 __ext4_check_dir_entry+0x7c2/0x970 fs/ext4/dir.c:85
 ext4_readdir+0x11ca/0x39b0 fs/ext4/dir.c:261
 iterate_dir+0x260/0x570 fs/readdir.c:-1
 __do_sys_getdents64 fs/readdir.c:369 [inline]
 __se_sys_getdents64+0xe5/0x240 fs/readdir.c:354
 __x64_sys_getdents64+0x7b/0x90 fs/readdir.c:354
 do_syscall_64+0x31/0x40 arch/x86/entry/common.c:46
 entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f0980203d29
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f097fc7d038 EFLAGS: 00000246 ORIG_RAX: 00000000000000d9
RAX: ffffffffffffffda RBX: 00007f09803f3fa0 RCX: 00007f0980203d29
RDX: 0000000000000010 RSI: 0000000000000000 RDI: 0000000000000005
RBP: 00007f098027fb08 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f09803f3fa0 R15: 00007ffcdf739b58

The buggy address belongs to the page:
page:ffffea0004afc5c0 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x12bf17
flags: 0x4000000000000000()
raw: 4000000000000000 ffffea0004afcf48 ffffea000495c188 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 0x100cca(GFP_HIGHUSER_MOVABLE), pid 496, ts 47675033807, free_ts 47856308197
 set_page_owner include/linux/page_owner.h:35 [inline]
 post_alloc_hook mm/page_alloc.c:2456 [inline]
 prep_new_page+0x179/0x180 mm/page_alloc.c:2462
 get_page_from_freelist+0x2235/0x23d0 mm/page_alloc.c:4254
 __alloc_pages_nodemask+0x268/0x5f0 mm/page_alloc.c:5370
 __alloc_pages include/linux/gfp.h:544 [inline]
 __alloc_pages_node include/linux/gfp.h:557 [inline]
 alloc_pages_node include/linux/gfp.h:571 [inline]
 alloc_pages include/linux/gfp.h:590 [inline]
 wp_page_copy+0x1fd/0x15d0 mm/memory.c:3171
 do_wp_page+0x9a6/0xc80 mm/memory.c:-1
 handle_pte_fault+0xac1/0x3750 mm/memory.c:4810
 __handle_mm_fault mm/memory.c:4944 [inline]
 handle_mm_fault+0xf3f/0x16a0 mm/memory.c:5358
 do_user_addr_fault+0x5a2/0xc80 arch/x86/mm/fault.c:1362
 handle_page_fault arch/x86/mm/fault.c:1428 [inline]
 exc_page_fault+0x5a/0xc0 arch/x86/mm/fault.c:1484
 asm_exc_page_fault+0x1e/0x30 arch/x86/include/asm/idtentry.h:571
page last free stack trace:
 reset_page_owner include/linux/page_owner.h:28 [inline]
 free_pages_prepare mm/page_alloc.c:1349 [inline]
 free_pcp_prepare mm/page_alloc.c:1421 [inline]
 free_unref_page_prepare+0x2b7/0x2d0 mm/page_alloc.c:3336
 free_unref_page_list+0x12e/0x9b0 mm/page_alloc.c:3443
 release_pages+0xe38/0xe80 mm/swap.c:1103
 free_pages_and_swap_cache+0x86/0xa0 mm/swap_state.c:356
 tlb_batch_pages_flush mm/mmu_gather.c:49 [inline]
 tlb_flush_mmu_free mm/mmu_gather.c:240 [inline]
 tlb_flush_mmu mm/mmu_gather.c:247 [inline]
 tlb_finish_mmu+0x175/0x300 mm/mmu_gather.c:326
 exit_mmap+0x2fc/0x540 mm/mmap.c:3387
 __mmput+0x93/0x2f0 kernel/fork.c:1153
 mmput+0x4e/0x150 kernel/fork.c:1176
 exit_mm kernel/exit.c:539 [inline]
 do_exit+0x9ae/0x2480 kernel/exit.c:859
 do_group_exit+0x141/0x310 kernel/exit.c:986
 __do_sys_exit_group kernel/exit.c:997 [inline]
 __se_sys_exit_group kernel/exit.c:995 [inline]
 __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:995
 do_syscall_64+0x31/0x40 arch/x86/entry/common.c:46
 entry_SYSCALL_64_after_hwframe+0x61/0xcb

Memory state around the buggy address:
 ffff88812bf16f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff88812bf16f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff88812bf17000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                   ^
 ffff88812bf17080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff88812bf17100: 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.18: path (unknown): bad entry in directory: rec_len is smaller than minimal - offset=1023, inode=0, rec_len=0, size=1024 fake=0