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 ffff888127d5a003 by task syz-executor.0/439 CPU: 0 PID: 439 Comm: syz-executor.0 Not tainted 6.1.75-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 Call Trace: __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:284 [inline] print_report+0x158/0x4e0 mm/kasan/report.c:395 kasan_report+0x13c/0x170 mm/kasan/report.c:495 __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/0x600 __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 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7fb2f9a7dd69 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:00007fb2fa7070c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000d9 RAX: ffffffffffffffda RBX: 00007fb2f9babf80 RCX: 00007fb2f9a7dd69 RDX: 0000000000000010 RSI: 0000000000000000 RDI: 0000000000000005 RBP: 00007fb2f9aca49e R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007fb2f9babf80 R15: 00007ffd19baf048 The buggy address belongs to the physical page: page:ffffea00049f5680 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x127d5a flags: 0x4000000000000000(zone=1) raw: 4000000000000000 ffffea00049f56c8 ffff8881f713b528 0000000000000000 raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner info is not present (never set?) Memory state around the buggy address: ffff888127d59f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff888127d59f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffff888127d5a000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff888127d5a080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff888127d5a100: 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-testdir3152540664/syzkaller.uFWYVD/0/file0: bad entry in directory: rec_len is smaller than minimal - offset=1023, inode=0, rec_len=0, size=1024 fake=0