EXT4-fs (loop0): mounted filesystem without journal. Opts: jqfmt=vfsold,grpid,debug,noload,noauto_da_alloc,commit=0x0000000000000005,init_itable=0x0000000000000009,debug,usrjquota=,nolazytime,mblk_io_submit,,errors=continue
EXT4-fs warning (device loop0): dx_probe:806: inode #2: comm syz-executor161: Unrecognised inode hash code 4
EXT4-fs warning (device loop0): dx_probe:946: inode #2: comm syz-executor161: 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 ffff888120b20003 by task syz-executor161/297
CPU: 0 PID: 297 Comm: syz-executor161 Not tainted 5.10.240-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/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:0x7fa33240d4a9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 18 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffeb26423d8 EFLAGS: 00000246 ORIG_RAX: 00000000000000d9
RAX: ffffffffffffffda RBX: 00007fa3324560e0 RCX: 00007fa33240d4a9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000006
RBP: 00007fa3324560a5 R08: 00007ffeb2642410 R09: 00007ffeb2642410
R10: 00007ffeb2642410 R11: 0000000000000246 R12: 00007ffeb26423fc
R13: 0000000000000004 R14: 431bde82d7b634db R15: 00007ffeb2642430
The buggy address belongs to the page:
page:ffffea000482c800 refcount:0 mapcount:-128 mapping:0000000000000000 index:0x1 pfn:0x120b20
flags: 0x4000000000000000()
raw: 4000000000000000 ffffea0004841608 ffffffff869f6988 0000000000000000
raw: 0000000000000001 0000000000000003 00000000ffffff7f 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 275, ts 28772159375, free_ts 28850287411
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:5357
__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:3383
__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:
ffff888120b1ff00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff888120b1ff80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff888120b20000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
^
ffff888120b20080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff888120b20100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================
EXT4-fs error (device loop0): ext4_readdir:263: inode #2: block 255: comm syz-executor161: path (unknown): bad entry in directory: rec_len % 4 != 0 - offset=1023, inode=2590052352, rec_len=28762, size=1024 fake=0