EXT4-fs: Warning: mounting with data=journal disables delayed allocation, dioread_nolock, O_DIRECT and fast_commit support!
EXT4-fs (loop2): encrypted files will use data=ordered instead of data journaling mode
EXT4-fs (loop2): 1 truncate cleaned up
EXT4-fs (loop2): mounted filesystem without journal. Opts: max_batch_time=0x0000000000000004,max_batch_time=0x0000000000000002,resuid=0x0000000000000000,block_validity,errors=remount-ro,nombcache,. Quota mode: none.
==================================================================
BUG: KASAN: use-after-free in ext4_read_inline_data fs/ext4/inline.c:210 [inline]
BUG: KASAN: use-after-free in ext4_convert_inline_data_nolock+0x313/0xcd0 fs/ext4/inline.c:1255
Read of size 68 at addr ffff888128445c80 by task syz.2.17/373
CPU: 0 PID: 373 Comm: syz.2.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
Call Trace:
<TASK>
__dump_stack+0x21/0x30 lib/dump_stack.c:88
dump_stack_lvl+0x110/0x170 lib/dump_stack.c:106
print_address_description+0x7f/0x2c0 mm/kasan/report.c:248
__kasan_report mm/kasan/report.c:427 [inline]
kasan_report+0x10f/0x150 mm/kasan/report.c:444
check_region_inline mm/kasan/generic.c:-1 [inline]
kasan_check_range+0x249/0x2a0 mm/kasan/generic.c:189
memcpy+0x2d/0x70 mm/kasan/shadow.c:65
ext4_read_inline_data fs/ext4/inline.c:210 [inline]
ext4_convert_inline_data_nolock+0x313/0xcd0 fs/ext4/inline.c:1255
ext4_try_add_inline_entry+0x737/0xa70 fs/ext4/inline.c:1381
ext4_add_entry+0x711/0x1020 fs/ext4/namei.c:2458
ext4_mkdir+0x520/0xc90 fs/ext4/namei.c:3081
vfs_mkdir+0x38b/0x590 fs/namei.c:4073
do_mkdirat+0x174/0x4d0 fs/namei.c:4098
__do_sys_mkdirat fs/namei.c:4113 [inline]
__se_sys_mkdirat fs/namei.c:4111 [inline]
__x64_sys_mkdirat+0x89/0xa0 fs/namei.c:4111
x64_sys_call+0x37e/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:259
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fe0b6dcfcc7
Code: 00 66 90 48 89 f2 b9 00 01 00 00 48 89 fe bf 9c ff ff ff e9 db f7 ff ff 66 2e 0f 1f 84 00 00 00 00 00 90 b8 02 01 00 00 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:00007ffda24ec2c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007ffda24ec350 RCX: 00007fe0b6dcfcc7
RDX: 00000000000001ff RSI: 0000200000000080 RDI: 00000000ffffff9c
RBP: 0000200000000140 R08: 0000200000000080 R09: 0000000000000000
R10: 0000200000000140 R11: 0000000000000246 R12: 0000200000000080
R13: 00007ffda24ec310 R14: 0000000000000000 R15: 0000000000000000
</TASK>
The buggy address belongs to the page:
page:ffffea0004a11140 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x128445
flags: 0x4000000000000000(zone=1)
raw: 4000000000000000 ffffea0004a11188 ffffea0004ae4bc8 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 357, ts 27304209391, free_ts 27333550093
set_page_owner include/linux/page_owner.h:33 [inline]
post_alloc_hook+0x192/0x1b0 mm/page_alloc.c:2605
prep_new_page+0x1c/0x110 mm/page_alloc.c:2611
get_page_from_freelist+0x2c3a/0x2cd0 mm/page_alloc.c:4485
__alloc_pages+0x1a2/0x460 mm/page_alloc.c:5822
__alloc_pages_node include/linux/gfp.h:595 [inline]
alloc_pages_node include/linux/gfp.h:609 [inline]
alloc_pages include/linux/gfp.h:622 [inline]
wp_page_copy+0x217/0x1890 mm/memory.c:3228
do_wp_page+0x9e1/0xc90 mm/memory.c:-1
handle_pte_fault+0x824/0x2770 mm/memory.c:4944
__handle_mm_fault mm/memory.c:-1 [inline]
do_handle_mm_fault+0x1b3b/0x1e30 mm/memory.c:5345
handle_mm_fault include/linux/mm.h:1847 [inline]
do_user_addr_fault+0x808/0x11c0 arch/x86/mm/fault.c:1416
handle_page_fault arch/x86/mm/fault.c:1507 [inline]
exc_page_fault+0x51/0xb0 arch/x86/mm/fault.c:1560
asm_exc_page_fault+0x27/0x30 arch/x86/include/asm/idtentry.h:606
page last free stack trace:
reset_page_owner include/linux/page_owner.h:26 [inline]
free_pages_prepare mm/page_alloc.c:1472 [inline]
free_pcp_prepare mm/page_alloc.c:1544 [inline]
free_unref_page_prepare+0x542/0x550 mm/page_alloc.c:3534
free_unref_page_list+0x138/0x9e0 mm/page_alloc.c:3671
release_pages+0x1264/0x12c0 mm/swap.c:1015
free_pages_and_swap_cache+0x86/0xa0 mm/swap_state.c:320
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+0x17e/0x310 mm/mmu_gather.c:338
exit_mmap+0x43b/0x8b0 mm/mmap.c:3248
__mmput+0x92/0x300 kernel/fork.c:1185
mmput+0x50/0x150 kernel/fork.c:1208
exit_mm kernel/exit.c:555 [inline]
do_exit+0xacc/0x29a0 kernel/exit.c:877
do_group_exit+0x149/0x310 kernel/exit.c:1004
get_signal+0x64f/0x1430 kernel/signal.c:2907
arch_do_signal_or_restart+0xe2/0x1100 arch/x86/kernel/signal.c:867
handle_signal_work kernel/entry/common.c:154 [inline]
exit_to_user_mode_loop+0xa7/0xe0 kernel/entry/common.c:178
exit_to_user_mode_prepare+0x87/0xd0 kernel/entry/common.c:214
__syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline]
syscall_exit_to_user_mode+0x1a/0x30 kernel/entry/common.c:307
do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:86
Memory state around the buggy address:
ffff888128445b80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff888128445c00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff888128445c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
^
ffff888128445d00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff888128445d80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================
EXT4-fs error (device loop2): ext4_check_all_de:667: inode #12: block 7: comm syz.2.17: bad entry in directory: directory entry overrun - offset=0, inode=901261600, rec_len=7976, size=124 fake=0
EXT4-fs (loop2): Remounting filesystem read-only