EXT4-fs error (device loop5): xattr_find_entry:297: inode #15: comm syz.5.779: corrupted xattr entries EXT4-fs error (device loop5): get_max_inline_xattr_value_size:69: inode #15: comm syz.5.779: corrupt xattr in inline inode ================================================================== BUG: KASAN: out-of-bounds in ext4_xattr_set_entry+0x13ba/0x3940 fs/ext4/xattr.c:1736 Read of size 18446744073709551600 at addr ffff88813c1f82b8 by task syz.5.779/3298 CPU: 1 PID: 3298 Comm: syz.5.779 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026 Call Trace: __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+0xf1/0x140 mm/kasan/report.c:444 check_region_inline mm/kasan/generic.c:-1 [inline] kasan_check_range+0x249/0x2a0 mm/kasan/generic.c:189 memmove+0x2d/0x70 mm/kasan/shadow.c:54 ext4_xattr_set_entry+0x13ba/0x3940 fs/ext4/xattr.c:1736 ext4_xattr_ibody_set+0x122/0x360 fs/ext4/xattr.c:2238 ext4_destroy_inline_data_nolock+0x234/0x5d0 fs/ext4/inline.c:468 ext4_convert_inline_data_to_extent fs/ext4/inline.c:633 [inline] ext4_try_to_write_inline_data+0x6ef/0x1190 fs/ext4/inline.c:774 ext4_write_begin+0x243/0x12e0 fs/ext4/inode.c:1192 ext4_da_write_begin+0x321/0xbf0 fs/ext4/inode.c:2988 generic_perform_write+0x2b7/0x690 mm/filemap.c:3870 ext4_buffered_write_iter+0x4ed/0x670 fs/ext4/file.c:270 ext4_file_write_iter+0x440/0x1540 fs/ext4/file.c:-1 call_write_iter include/linux/fs.h:2212 [inline] new_sync_write fs/read_write.c:507 [inline] vfs_write+0x835/0xfd0 fs/read_write.c:594 ksys_write+0x149/0x250 fs/read_write.c:647 __do_sys_write fs/read_write.c:659 [inline] __se_sys_write fs/read_write.c:656 [inline] __x64_sys_write+0x7b/0x90 fs/read_write.c:656 x64_sys_call+0x8ef/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:2 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:0x7fd5d3293819 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 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 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fd5d1cee028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007fd5d350cfa0 RCX: 00007fd5d3293819 RDX: 0000000000001006 RSI: 0000200000001680 RDI: 0000000000000005 RBP: 00007fd5d3329c91 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fd5d350d038 R14: 00007fd5d350cfa0 R15: 00007ffd41b52808 The buggy address belongs to the page: page:ffffea0004f07e00 refcount:3 mapcount:1 mapping:ffff8881092cd358 index:0x2 pfn:0x13c1f8 memcg:ffff888100254500 aops:def_blk_aops ino:700005 flags: 0x400000000002203e(referenced|uptodate|dirty|lru|active|private|mappedtodisk|zone=1) raw: 400000000002203e ffffea0004c28f48 ffffea0004df8308 ffff8881092cd358 raw: 0000000000000002 ffff888129a57c78 0000000300000000 ffff888100254500 page dumped because: kasan: bad access detected page_owner tracks the page as allocated page last allocated via order 0, migratetype Movable, gfp_mask 0x108c48(GFP_NOFS|__GFP_NOFAIL|__GFP_HARDWALL|__GFP_MOVABLE), pid 3298, ts 143252907048, free_ts 143252763685 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+0x2d3a/0x2dc0 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] __page_cache_alloc include/linux/pagemap.h:305 [inline] pagecache_get_page+0xac6/0xde0 mm/filemap.c:1955 find_or_create_page include/linux/pagemap.h:418 [inline] grow_dev_page fs/buffer.c:949 [inline] grow_buffers fs/buffer.c:1014 [inline] __getblk_slow fs/buffer.c:1041 [inline] __getblk_gfp+0x238/0x7d0 fs/buffer.c:1336 sb_getblk include/linux/buffer_head.h:361 [inline] __ext4_get_inode_loc+0x46e/0xcd0 fs/ext4/inode.c:4363 __ext4_get_inode_loc_noinmem fs/ext4/inode.c:4471 [inline] __ext4_iget+0x448/0x3e50 fs/ext4/inode.c:4726 ext4_lookup+0x4b4/0x960 fs/ext4/namei.c:1858 lookup_open fs/namei.c:3448 [inline] open_last_lookups fs/namei.c:3540 [inline] path_openat+0xfc9/0x2f20 fs/namei.c:3747 do_filp_open+0x1e2/0x410 fs/namei.c:3777 do_sys_openat2+0x15e/0x7f0 fs/open.c:1236 do_sys_open fs/open.c:1252 [inline] __do_sys_creat fs/open.c:1328 [inline] __se_sys_creat fs/open.c:1322 [inline] __x64_sys_creat+0x8e/0xb0 fs/open.c:1322 x64_sys_call+0x94a/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:86 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 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+0x13a/0x9d0 mm/page_alloc.c:3671 release_pages+0x1006/0x1060 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+0x93/0x320 kernel/fork.c:1180 mmput+0x50/0x150 kernel/fork.c:1203 free_bprm+0x14c/0x300 fs/exec.c:1507 do_execveat_common+0x92e/0xa80 fs/exec.c:1972 do_execve fs/exec.c:2040 [inline] __do_sys_execve fs/exec.c:2116 [inline] __se_sys_execve fs/exec.c:2111 [inline] __x64_sys_execve+0x92/0xb0 fs/exec.c:2111 x64_sys_call+0x919/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:60 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 Memory state around the buggy address: ffff88813c1f8180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff88813c1f8200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffff88813c1f8280: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ^ ffff88813c1f8300: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff88813c1f8380: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ================================================================== EXT4-fs error (device loop5): ext4_mb_mark_diskspace_used:3885: comm syz.5.779: Allocating blocks 385-513 which overlap fs metadata