EXT4-fs (sda1): Ignoring removed bh option
==================================================================
BUG: KASAN: use-after-free in ext4_xattr_set_entry+0x33cb/0x3710 fs/ext4/xattr.c:1599
Read of size 4 at addr ffff88806c9d0527 by task syz-executor.4/20946

CPU: 0 PID: 20946 Comm: syz-executor.4 Not tainted 5.0.0+ #5
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x172/0x1f0 lib/dump_stack.c:113
 print_address_description.cold+0x7c/0x20d mm/kasan/report.c:187
 kasan_report.cold+0x1b/0x40 mm/kasan/report.c:317
 __asan_report_load4_noabort+0x14/0x20 mm/kasan/generic_report.c:134
EXT4-fs error (device sda1): ext4_xattr_set_entry:1602: inode #17739: comm syz-executor.5: corrupted xattr entries
 ext4_xattr_set_entry+0x33cb/0x3710 fs/ext4/xattr.c:1599
 ext4_xattr_ibody_set+0x80/0x2b0 fs/ext4/xattr.c:2235
 ext4_xattr_set_handle+0x5d2/0x1010 fs/ext4/xattr.c:2391
 ext4_initxattrs+0xc0/0x130 fs/ext4/xattr_security.c:43
 security_inode_init_security security/security.c:526 [inline]
 security_inode_init_security+0x2d1/0x3c0 security/security.c:499
 ext4_init_security+0x34/0x40 fs/ext4/xattr_security.c:57
 __ext4_new_inode+0x3b23/0x52c0 fs/ext4/ialloc.c:1160
 ext4_symlink+0x3f8/0xbe0 fs/ext4/namei.c:3096
 vfs_symlink fs/namei.c:4126 [inline]
 vfs_symlink+0x378/0x5d0 fs/namei.c:4112
 do_symlinkat+0x22b/0x290 fs/namei.c:4153
 __do_sys_symlink fs/namei.c:4172 [inline]
 __se_sys_symlink fs/namei.c:4170 [inline]
 __x64_sys_symlink+0x59/0x80 fs/namei.c:4170
 do_syscall_64+0x103/0x610 arch/x86/entry/common.c:290
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x457b57
Code: 0f 1f 00 b8 5c 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 6d bb fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 b8 58 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f 83 4d bb fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007ffe4a82dd68 EFLAGS: 00000202 ORIG_RAX: 0000000000000058
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 0000000000457b57
RDX: 00007ffe4a82dde7 RSI: 00000000004bd615 RDI: 00007ffe4a82ddd0
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000017
R10: 0000000000000075 R11: 0000000000000202 R12: 0000000000000000
R13: 0000000000000001 R14: 00000000000004f5 R15: 0000000000000004
EXT4-fs error (device sda1): ext4_xattr_set_entry:1602: inode #16520: comm syz-executor.2: corrupted xattr entries

The buggy address belongs to the page:
page:ffffea0001b27400 count:0 mapcount:-128 mapping:0000000000000000 index:0x1
flags: 0x1fffc0000000000()
raw: 01fffc0000000000 ffffea0001b24808 ffffea0001b20c08 0000000000000000
raw: 0000000000000001 0000000000000004 00000000ffffff7f 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff88806c9d0400: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff88806c9d0480: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff88806c9d0500: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                               ^
 ffff88806c9d0580: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff88806c9d0600: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================
EXT4-fs error (device sda1): ext4_xattr_ibody_get:591: inode #16520: comm syz-executor.0: corrupted in-inode xattr
EXT4-fs error (device sda1): ext4_xattr_set_entry:1602: inode #16521: comm syz-executor.5: corrupted xattr entries