================================================================== BUG: KASAN: use-after-free in ext4_xattr_delete_inode+0xba6/0xbb0 fs/ext4/xattr.c:2911 Read of size 4 at addr ffff888124d0e000 by task syz-executor/422 CPU: 0 PID: 422 Comm: syz-executor Not tainted 5.15.180-syzkaller-1080043-g88c4075c39ed #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025 Call Trace: __dump_stack+0x21/0x30 lib/dump_stack.c:88 dump_stack_lvl+0xee/0x150 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+0xf1/0x140 mm/kasan/report.c:444 __asan_report_load4_noabort+0x14/0x20 mm/kasan/report_generic.c:308 ext4_xattr_delete_inode+0xba6/0xbb0 fs/ext4/xattr.c:2911 ext4_evict_inode+0xe44/0x1450 fs/ext4/inode.c:300 evict+0x485/0x870 fs/inode.c:647 iput_final fs/inode.c:1769 [inline] iput+0x635/0x7c0 fs/inode.c:1795 d_delete_notify include/linux/fsnotify.h:278 [inline] vfs_rmdir+0x33f/0x460 fs/namei.c:4162 do_rmdir+0x259/0x6a0 fs/namei.c:4210 __do_sys_unlinkat fs/namei.c:4390 [inline] __se_sys_unlinkat fs/namei.c:4384 [inline] __x64_sys_unlinkat+0xc7/0xf0 fs/namei.c:4384 x64_sys_call+0x4c0/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:264 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:0x7ff3467c85d7 Code: 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 07 01 00 00 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:00007fff58939a78 EFLAGS: 00000207 ORIG_RAX: 0000000000000107 RAX: ffffffffffffffda RBX: 0000000000000065 RCX: 00007ff3467c85d7 RDX: 0000000000000200 RSI: 00007fff5893ac20 RDI: 00000000ffffff9c RBP: 00007ff34683b134 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000100 R11: 0000000000000207 R12: 00007fff5893ac20 R13: 00007ff34683b134 R14: 000000000000ccf8 R15: 00007fff5893cdd0 The buggy address belongs to the page: page:ffffea0004934380 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x124d0e flags: 0x4000000000000000(zone=1) raw: 4000000000000000 ffffea0004934148 ffffea0004a1d788 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 432, ts 52593549831, free_ts 52600133855 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+0x2cc5/0x2d50 mm/page_alloc.c:4485 __alloc_pages+0x18f/0x440 mm/page_alloc.c:5781 __alloc_pages_node include/linux/gfp.h:591 [inline] alloc_pages_node include/linux/gfp.h:605 [inline] alloc_pages include/linux/gfp.h:618 [inline] wp_page_copy+0x20f/0x18f0 mm/memory.c:3225 do_wp_page+0x731/0xc90 mm/memory.c:-1 handle_pte_fault+0x73c/0x2680 mm/memory.c:4931 __handle_mm_fault mm/memory.c:-1 [inline] do_handle_mm_fault+0x1a6d/0x1d50 mm/memory.c:5332 do_user_addr_fault+0x554/0x1180 arch/x86/mm/fault.c:1325 handle_page_fault arch/x86/mm/fault.c:1509 [inline] exc_page_fault+0x51/0xb0 arch/x86/mm/fault.c:1565 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+0x134/0x9d0 mm/page_alloc.c:3671 release_pages+0x1076/0x10d0 mm/swap.c:1009 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+0x175/0x300 mm/mmu_gather.c:338 exit_mmap+0x40f/0x860 mm/mmap.c:3236 __mmput+0x93/0x320 kernel/fork.c:1180 mmput+0x50/0x150 kernel/fork.c:1203 exit_mm kernel/exit.c:554 [inline] do_exit+0x9ca/0x27a0 kernel/exit.c:867 do_group_exit+0x141/0x310 kernel/exit.c:1002 get_signal+0x66a/0x1480 kernel/signal.c:2907 arch_do_signal_or_restart+0xc1/0x10f0 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+0x5a/0xa0 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: ffff888124d0df00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff888124d0df80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffff888124d0e000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff888124d0e080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff888124d0e100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ================================================================== EXT4-fs error (device loop0): ext4_xattr_inode_iget:404: comm syz-executor: inode #1: comm syz-executor: iget: illegal inode # EXT4-fs error (device loop0): ext4_xattr_inode_iget:409: comm syz-executor: error while reading EA inode 1 err=-117