================================================================== BUG: KASAN: use-after-free in get_max_inline_xattr_value_size+0x373/0x510 fs/ext4/inline.c:61 Read of size 4 at addr ffff8881de7e4084 by task syz-executor374/300 CPU: 0 PID: 300 Comm: syz-executor374 Not tainted 5.4.219-syzkaller-00013-g4a947285bcca #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1d8/0x241 lib/dump_stack.c:118 print_address_description+0x8c/0x630 mm/kasan/report.c:384 __kasan_report+0xf6/0x130 mm/kasan/report.c:516 kasan_report+0x30/0x60 mm/kasan/common.c:653 get_max_inline_xattr_value_size+0x373/0x510 fs/ext4/inline.c:61 ext4_get_max_inline_size+0x139/0x1f0 fs/ext4/inline.c:112 ext4_try_to_write_inline_data+0xd9/0x1750 fs/ext4/inline.c:673 ext4_write_begin+0x247/0x1d50 fs/ext4/inode.c:1312 ext4_da_write_begin+0x4a8/0xf80 fs/ext4/inode.c:3110 generic_perform_write+0x2f9/0x5a0 mm/filemap.c:3311 __generic_file_write_iter+0x239/0x490 mm/filemap.c:3440 ext4_file_write_iter+0x495/0x10e0 fs/ext4/file.c:270 call_write_iter include/linux/fs.h:1976 [inline] new_sync_write fs/read_write.c:483 [inline] __vfs_write+0x5e3/0x780 fs/read_write.c:496 vfs_write+0x210/0x4f0 fs/read_write.c:558 ksys_write+0x198/0x2c0 fs/read_write.c:611 do_syscall_64+0xcb/0x1c0 arch/x86/entry/common.c:290 entry_SYSCALL_64_after_hwframe+0x5c/0xc1 Allocated by task 295: save_stack mm/kasan/common.c:70 [inline] set_track mm/kasan/common.c:78 [inline] __kasan_kmalloc+0x131/0x1e0 mm/kasan/common.c:529 slab_post_alloc_hook mm/slab.h:584 [inline] slab_alloc_node mm/slub.c:2829 [inline] slab_alloc mm/slub.c:2837 [inline] kmem_cache_alloc+0xd0/0x210 mm/slub.c:2842 kmem_cache_zalloc include/linux/slab.h:680 [inline] __alloc_file+0x26/0x300 fs/file_table.c:101 alloc_empty_file+0xa9/0x1b0 fs/file_table.c:151 path_openat+0x116/0x3ea0 fs/namei.c:3603 do_filp_open+0x208/0x450 fs/namei.c:3644 do_sys_open+0x393/0x7e0 fs/open.c:1113 do_syscall_64+0xcb/0x1c0 arch/x86/entry/common.c:290 entry_SYSCALL_64_after_hwframe+0x5c/0xc1 Freed by task 9: save_stack mm/kasan/common.c:70 [inline] set_track mm/kasan/common.c:78 [inline] kasan_set_free_info mm/kasan/common.c:345 [inline] __kasan_slab_free+0x178/0x240 mm/kasan/common.c:487 slab_free_hook mm/slub.c:1455 [inline] slab_free_freelist_hook+0x80/0x150 mm/slub.c:1494 slab_free mm/slub.c:3080 [inline] kmem_cache_free+0xa9/0x1d0 mm/slub.c:3096 __rcu_reclaim kernel/rcu/rcu.h:222 [inline] rcu_do_batch+0x49e/0xa10 kernel/rcu/tree.c:2167 rcu_core+0x4ba/0xca0 kernel/rcu/tree.c:2387 __do_softirq+0x23e/0x643 kernel/softirq.c:292 The buggy address belongs to the object at ffff8881de7e4000 which belongs to the cache filp of size 280 The buggy address is located 132 bytes inside of 280-byte region [ffff8881de7e4000, ffff8881de7e4118) The buggy address belongs to the page: page:ffffea000779f900 refcount:1 mapcount:0 mapping:ffff8881f5cf8500 index:0x0 compound_mapcount: 0 flags: 0x8000000000010200(slab|head) raw: 8000000000010200 dead000000000100 dead000000000122 ffff8881f5cf8500 raw: 0000000000000000 0000000000150015 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner tracks the page as allocated page last allocated via order 1, migratetype Unmovable, gfp_mask 0xd20c0(__GFP_IO|__GFP_FS|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC) set_page_owner include/linux/page_owner.h:31 [inline] post_alloc_hook mm/page_alloc.c:2165 [inline] prep_new_page+0x194/0x380 mm/page_alloc.c:2171 get_page_from_freelist+0x524/0x560 mm/page_alloc.c:3794 __alloc_pages_nodemask+0x372/0x860 mm/page_alloc.c:4891 alloc_slab_page+0x39/0x3e0 mm/slub.c:343 allocate_slab mm/slub.c:1683 [inline] new_slab+0x97/0x450 mm/slub.c:1749 new_slab_objects mm/slub.c:2505 [inline] ___slab_alloc+0x320/0x4a0 mm/slub.c:2667 __slab_alloc+0x5a/0x90 mm/slub.c:2707 slab_alloc_node mm/slub.c:2792 [inline] slab_alloc mm/slub.c:2837 [inline] kmem_cache_alloc+0x100/0x210 mm/slub.c:2842 kmem_cache_zalloc include/linux/slab.h:680 [inline] __alloc_file+0x26/0x300 fs/file_table.c:101 alloc_empty_file+0xa9/0x1b0 fs/file_table.c:151 path_openat+0x116/0x3ea0 fs/namei.c:3603 do_filp_open+0x208/0x450 fs/namei.c:3644 do_sys_open+0x393/0x7e0 fs/open.c:1113 do_syscall_64+0xcb/0x1c0 arch/x86/entry/common.c:290 entry_SYSCALL_64_after_hwframe+0x5c/0xc1 page_owner free stack trace missing Memory state around the buggy address: ffff8881de7e3f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff8881de7e4000: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb >ffff8881de7e4080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff8881de7e4100: fb fb fb fc fc fc fc fc fc fc fc fc fc fc fc fc ffff8881de7e4180: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ================================================================== EXT4-fs error (device loop0): ext4_read_block_bitmap_nowait:430: comm syz-executor374: Invalid block bitmap block 0 in block_group 0 syz-executor374 (300) used greatest stack depth: 22872 bytes left