EXT4-fs error (device loop1): ext4_xattr_ibody_get:591: inode #18: comm syz-executor.1: corrupted in-inode xattr
==================================================================
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 ffff88816a84d084 by task syz-executor.1/16585

CPU: 1 PID: 16585 Comm: syz-executor.1 Not tainted 5.4.219-syzkaller-00002-ga0eae55f26a0 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023
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
 do_iter_readv_writev+0x529/0x740 fs/read_write.c:690
 do_iter_write+0x16f/0x570 fs/read_write.c:970
 iter_file_splice_write+0x887/0x10f0 fs/splice.c:746
 splice_direct_to_actor+0x4c4/0xb20 fs/splice.c:976
 do_splice_direct+0x2a0/0x3f0 fs/splice.c:1064
 do_sendfile+0x8f2/0xf10 fs/read_write.c:1464
 __do_sys_sendfile64 fs/read_write.c:1525 [inline]
 __se_sys_sendfile64 fs/read_write.c:1511 [inline]
 __x64_sys_sendfile64+0x1ce/0x230 fs/read_write.c:1511
 do_syscall_64+0xcb/0x1c0 arch/x86/entry/common.c:290
 entry_SYSCALL_64_after_hwframe+0x5c/0xc1

The buggy address belongs to the page:
page:ffffea0005aa1340 refcount:0 mapcount:0 mapping:0000000000000000 index:0x0
flags: 0x8000000000000000()
raw: 8000000000000000 ffffea0005aa1388 ffffea00059f2dc8 0000000000000000
raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as freed
page last allocated via order 0, migratetype Unmovable, gfp_mask 0x500dc0(GFP_USER|__GFP_ZERO|__GFP_ACCOUNT)
 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_pages include/linux/gfp.h:503 [inline]
 __alloc_pages_node include/linux/gfp.h:516 [inline]
 alloc_pages_node include/linux/gfp.h:530 [inline]
 __pte_alloc_one include/asm-generic/pgalloc.h:63 [inline]
 pte_alloc_one+0x1b/0xb0 arch/x86/mm/pgtable.c:26
 __pte_alloc+0x1d/0x1c0 mm/memory.c:439
 copy_pte_range+0xffa/0x16f0 mm/memory.c:829
 copy_pmd_range mm/memory.c:905 [inline]
 copy_pud_range mm/memory.c:939 [inline]
 copy_p4d_range mm/memory.c:961 [inline]
 copy_page_range+0x80a/0xbc0 mm/memory.c:1023
 dup_mmap+0x860/0xbe0 kernel/fork.c:605
 dup_mm+0x8c/0x300 kernel/fork.c:1368
 copy_mm+0xe8/0x180 kernel/fork.c:1424
 copy_process+0x1284/0x3230 kernel/fork.c:2041
 _do_fork+0x196/0x8d0 kernel/fork.c:2391
 __do_sys_clone kernel/fork.c:2549 [inline]
 __se_sys_clone kernel/fork.c:2530 [inline]
 __x64_sys_clone+0x287/0x2f0 kernel/fork.c:2530
 do_syscall_64+0xcb/0x1c0 arch/x86/entry/common.c:290
 entry_SYSCALL_64_after_hwframe+0x5c/0xc1
page last free stack trace:
 reset_page_owner include/linux/page_owner.h:24 [inline]
 free_pages_prepare mm/page_alloc.c:1176 [inline]
 free_pcp_prepare+0x1a4/0x290 mm/page_alloc.c:1233
 free_unref_page_prepare mm/page_alloc.c:3085 [inline]
 free_unref_page_list+0x11e/0x6e0 mm/page_alloc.c:3154
 release_pages+0xa46/0xa80 mm/swap.c:842
 tlb_batch_pages_flush mm/mmu_gather.c:49 [inline]
 tlb_flush_mmu_free mm/mmu_gather.c:184 [inline]
 tlb_flush_mmu+0x77f/0x910 mm/mmu_gather.c:191
 tlb_finish_mmu+0xcb/0x200 mm/mmu_gather.c:272
 exit_mmap+0x2e8/0x540 mm/mmap.c:3188
 __mmput+0x34/0x240 kernel/fork.c:1090
 exit_mm kernel/exit.c:489 [inline]
 do_exit+0xc44/0x2d30 kernel/exit.c:799
 do_group_exit+0x136/0x300 kernel/exit.c:910
 get_signal+0xd99/0x13f0 kernel/signal.c:2735
 do_signal+0xb0/0x1200 arch/x86/kernel/signal.c:809
 exit_to_usermode_loop+0xdd/0x1d0 arch/x86/entry/common.c:159
 prepare_exit_to_usermode+0x17c/0x1d0 arch/x86/entry/common.c:194
 entry_SYSCALL_64_after_hwframe+0x5c/0xc1

Memory state around the buggy address:
 ffff88816a84cf80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff88816a84d000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff88816a84d080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                   ^
 ffff88816a84d100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff88816a84d180: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================
EXT4-fs error (device loop1): ext4_read_block_bitmap_nowait:430: comm syz-executor.1: Invalid block bitmap block 0 in block_group 0