EXT4-fs error (device sda1): ext4_xattr_set_entry:1605: inode #16535: comm syz-executor.2: corrupted xattr entries EXT4-fs error (device sda1): ext4_xattr_set_entry:1605: inode #16539: comm syz-executor.0: corrupted xattr entries ================================================================== BUG: KASAN: use-after-free in memset include/linux/string.h:332 [inline] BUG: KASAN: use-after-free in __ext4_expand_extra_isize+0x14f/0x220 fs/ext4/inode.c:5754 Write of size 4062 at addr ffff88806b35f0a0 by task syz-executor.3/6854 CPU: 0 PID: 6854 Comm: syz-executor.3 Not tainted 4.14.143 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:17 [inline] dump_stack+0x138/0x197 lib/dump_stack.c:53 print_address_description.cold+0x7c/0x1dc mm/kasan/report.c:252 kasan_report_error mm/kasan/report.c:351 [inline] kasan_report mm/kasan/report.c:409 [inline] kasan_report.cold+0xa9/0x2af mm/kasan/report.c:393 check_memory_region_inline mm/kasan/kasan.c:260 [inline] check_memory_region+0x123/0x190 mm/kasan/kasan.c:267 memset+0x24/0x40 mm/kasan/kasan.c:285 memset include/linux/string.h:332 [inline] __ext4_expand_extra_isize+0x14f/0x220 fs/ext4/inode.c:5754 ext4_try_to_expand_extra_isize fs/ext4/inode.c:5806 [inline] ext4_mark_inode_dirty+0x664/0x860 fs/ext4/inode.c:5882 ext4_evict_inode+0x877/0x15c0 fs/ext4/inode.c:281 evict+0x2e6/0x630 fs/inode.c:554 iput_final fs/inode.c:1516 [inline] iput fs/inode.c:1543 [inline] iput+0x471/0x900 fs/inode.c:1528 do_unlinkat+0x38b/0x600 fs/namei.c:4095 SYSC_unlink fs/namei.c:4136 [inline] SyS_unlink+0x1b/0x20 fs/namei.c:4134 do_syscall_64+0x1e8/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x42/0xb7 RIP: 0033:0x459637 RSP: 002b:00007ffc332a4b58 EFLAGS: 00000246 ORIG_RAX: 0000000000000057 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 0000000000459637 RDX: 00007ffc332a4b70 RSI: 00007ffc332a4b70 RDI: 00007ffc332a4c00 RBP: 0000000000000396 R08: 0000000000000000 R09: 0000000000000009 R10: 0000000000000003 R11: 0000000000000246 R12: 00007ffc332a5c90 R13: 0000000002281940 R14: 0000000000000000 R15: 00007ffc332a5c90 The buggy address belongs to the page: page:ffffea0001acd7c0 count:2 mapcount:0 mapping:ffff8880a45adb60 index:0x45d flags: 0x1fffc0000001074(referenced|dirty|lru|active|private) raw: 01fffc0000001074 ffff8880a45adb60 000000000000045d 00000002ffffffff raw: ffffea0001962c20 ffffea000224cba0 ffff88807f4d52a0 ffff88821b7321c0 page dumped because: kasan: bad access detected page->mem_cgroup:ffff88821b7321c0 Memory state around the buggy address: ffff88806b35ff00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff88806b35ff80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffff88806b360000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff88806b360080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff88806b360100: 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:590: inode #16486: comm syz-executor.4: corrupted in-inode xattr