EXT4-fs error (device loop0): htree_dirblock_to_tree:1112: inode #2: block 20: comm syz-executor: bad entry in directory: inode out of bounds - offset=1024, inode=2033530174, rec_len=1012, size=1024 fake=0 EXT4-fs error (device loop0): htree_dirblock_to_tree:1112: inode #2: block 20: comm syz-executor: bad entry in directory: inode out of bounds - offset=1024, inode=2033530174, rec_len=1012, size=1024 fake=0 ================================================================== BUG: KASAN: use-after-free in ext4_htree_fill_tree+0x1066/0x10d0 fs/ext4/namei.c:1246 Read of size 1 at addr ffff888115eb2365 by task syz-executor/466 CPU: 0 PID: 466 Comm: syz-executor Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025 Call Trace: __dump_stack+0x21/0x24 lib/dump_stack.c:88 dump_stack_lvl+0xee/0x150 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_load1_noabort+0x14/0x20 mm/kasan/report_generic.c:348 ext4_htree_fill_tree+0x1066/0x10d0 fs/ext4/namei.c:1246 ext4_dx_readdir fs/ext4/dir.c:608 [inline] ext4_readdir+0x2d8a/0x3c10 fs/ext4/dir.c:145 iterate_dir+0x271/0x610 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 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:0x7f2445bbf753 Code: c1 66 0f 1f 44 00 00 48 83 c4 08 48 89 ef 5b 5d e9 52 3e f8 ff 66 90 b8 ff ff ff 7f 48 39 c2 48 0f 47 d0 b8 d9 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 05 c3 0f 1f 40 00 48 c7 c2 a8 ff ff ff f7 d8 RSP: 002b:00007ffc62afd338 EFLAGS: 00000293 ORIG_RAX: 00000000000000d9 RAX: ffffffffffffffda RBX: 0000555559c39560 RCX: 00007f2445bbf753 RDX: 0000000000008000 RSI: 0000555559c39560 RDI: 0000000000000007 RBP: 0000555559c39534 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000001000 R11: 0000000000000293 R12: ffffffffffffffa8 R13: 0000000000000010 R14: 0000555559c39530 R15: 00007ffc62b017d0 The buggy address belongs to the physical page: page:ffffea000457ac80 refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x115eb2 flags: 0x4000000000000000(zone=1) raw: 4000000000000000 ffffea000457d488 ffffea000457ac48 0000000000000000 raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner tracks the page as freed page last allocated via order 0, migratetype Unmovable, gfp_mask 0x102dc2(GFP_HIGHUSER|__GFP_NOWARN|__GFP_ZERO), pid 520, tgid 520 (syz.0.16), ts 50130083907, free_ts 50613583761 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+0x2c7b/0x2cf0 mm/page_alloc.c:4554 __alloc_pages+0x1c3/0x450 mm/page_alloc.c:5868 __alloc_pages_bulk+0x3bd/0x9c0 mm/page_alloc.c:5813 alloc_pages_bulk_array_node include/linux/gfp.h:209 [inline] vm_area_alloc_pages mm/vmalloc.c:2986 [inline] __vmalloc_area_node mm/vmalloc.c:3084 [inline] __vmalloc_node_range+0x6bb/0x13d0 mm/vmalloc.c:3256 alloc_thread_stack_node kernel/fork.c:320 [inline] dup_task_struct+0x3ae/0x790 kernel/fork.c:1081 copy_process+0x5b8/0x3480 kernel/fork.c:2287 kernel_clone+0x23a/0x810 kernel/fork.c:2874 __do_sys_clone3 kernel/fork.c:3175 [inline] __se_sys_clone3 kernel/fork.c:3159 [inline] __x64_sys_clone3+0x28d/0x2e0 kernel/fork.c:3159 x64_sys_call+0x4ce/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:436 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 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+0x8f/0x530 mm/page_alloc.c:3687 free_the_page mm/page_alloc.c:836 [inline] __free_pages+0x67/0x100 mm/page_alloc.c:5957 __vunmap+0x9af/0xb70 mm/vmalloc.c:2739 free_work+0x5a/0x80 mm/vmalloc.c:98 process_one_work+0x71f/0xc40 kernel/workqueue.c:2302 worker_thread+0xa29/0x11f0 kernel/workqueue.c:2449 kthread+0x281/0x320 kernel/kthread.c:386 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295 Memory state around the buggy address: ffff888115eb2200: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff888115eb2280: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >ffff888115eb2300: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff888115eb2380: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff888115eb2400: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ================================================================== EXT4-fs error (device loop0): htree_dirblock_to_tree:1112: inode #2: block 20: comm syz-executor: bad entry in directory: inode out of bounds - offset=1024, inode=2033530174, rec_len=1012, size=1024 fake=0 EXT4-fs error (device loop0): htree_dirblock_to_tree:1112: inode #2: block 20: comm syz-executor: bad entry in directory: inode out of bounds - offset=1024, inode=2033530174, rec_len=1012, size=1024 fake=0 EXT4-fs error (device loop0): htree_dirblock_to_tree:1112: inode #2: block 20: comm syz-executor: bad entry in directory: inode out of bounds - offset=1024, inode=2033530174, rec_len=1012, size=1024 fake=0 EXT4-fs error (device loop0): htree_dirblock_to_tree:1112: inode #2: block 20: comm syz-executor: bad entry in directory: inode out of bounds - offset=1024, inode=2033530174, rec_len=1012, size=1024 fake=0 EXT4-fs error (device loop0): htree_dirblock_to_tree:1112: inode #2: block 20: comm syz-executor: bad entry in directory: inode out of bounds - offset=1024, inode=2033530174, rec_len=1012, size=1024 fake=0 EXT4-fs (loop0): unmounting filesystem.