EXT4-fs error (device loop0): ext4_mb_mark_diskspace_used:4183: comm syz.0.0: Allocating blocks 497-513 which overlap fs metadata
EXT4-fs (loop0): pa ffff888043a210e8: logic 24576, phys. 273, len 15
EXT4-fs error (device loop0): ext4_mb_release_inode_pa:5434: group 0, free 8, pa_free 9
==================================================================
BUG: KASAN: use-after-free in ext4_ext_rm_leaf fs/ext4/extents.c:2627 [inline]
BUG: KASAN: use-after-free in ext4_ext_remove_space+0x3211/0x42f0 fs/ext4/extents.c:2965
Read of size 4 at addr ffff88804ca98c18 by task syz.0.0/5369

CPU: 0 UID: 0 PID: 5369 Comm: syz.0.0 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 print_address_description mm/kasan/report.c:378 [inline]
 print_report+0xca/0x240 mm/kasan/report.c:482
 kasan_report+0x118/0x150 mm/kasan/report.c:595
 ext4_ext_rm_leaf fs/ext4/extents.c:2627 [inline]
 ext4_ext_remove_space+0x3211/0x42f0 fs/ext4/extents.c:2965
 ext4_ext_truncate+0x17e/0x300 fs/ext4/extents.c:4484
 ext4_truncate+0xb4f/0x12e0 fs/ext4/inode.c:4643
 ext4_truncate_failed_write fs/ext4/truncate.h:22 [inline]
 ext4_write_begin+0x1150/0x19a0 fs/ext4/inode.c:1385
 ext4_da_write_begin+0x445/0xda0 fs/ext4/inode.c:3129
 generic_perform_write+0x2c5/0x900 mm/filemap.c:4175
 ext4_buffered_write_iter+0xce/0x3a0 fs/ext4/file.c:299
 ext4_file_write_iter+0x298/0x1bc0 fs/ext4/file.c:-1
 __kernel_write_iter+0x428/0x910 fs/read_write.c:619
 dump_emit_page fs/coredump.c:1296 [inline]
 dump_user_range+0x8a0/0xc90 fs/coredump.c:1370
 elf_core_dump+0x337b/0x3990 fs/binfmt_elf.c:2085
 coredump_write+0x1169/0x1900 fs/coredump.c:1049
 vfs_coredump+0x1daa/0x2a50 fs/coredump.c:1168
 get_signal+0x1109/0x1340 kernel/signal.c:3019
 arch_do_signal_or_restart+0x9a/0x750 arch/x86/kernel/signal.c:337
 exit_to_user_mode_loop kernel/entry/common.c:40 [inline]
 exit_to_user_mode_prepare include/linux/irq-entry-common.h:225 [inline]
 irqentry_exit_to_user_mode+0x81/0x120 kernel/entry/common.c:73
 exc_page_fault+0x9f/0xf0 arch/x86/mm/fault.c:1535
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623
RIP: 0033:0x7fc9c9b8eed1
Code: 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f
RSP: 002b:fffffffffffffe70 EFLAGS: 00010217
RAX: 0000000000000000 RBX: 00007fc9c9de5fa0 RCX: 00007fc9c9b8eec9
RDX: 0000000000000000 RSI: fffffffffffffe70 RDI: 0000000000008000
RBP: 00007fc9c9c11f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000000
R13: 00007fc9c9de6038 R14: 00007fc9c9de5fa0 R15: 00007ffdd573c428
 </TASK>

The buggy address belongs to the physical page:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x4ca98
flags: 0x4fff00000000000(node=1|zone=1|lastcpupid=0x7ff)
raw: 04fff00000000000 ffffea000132a648 ffffea000132a5c8 0000000000000000
raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner info is not present (never set?)

Memory state around the buggy address:
 ffff88804ca98b00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff88804ca98b80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff88804ca98c00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                            ^
 ffff88804ca98c80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff88804ca98d00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================