【hulk4.19】KASAN: use-after-free Write in ext4_xattr_set_entry

#### report
```
EXT4-fs error (device loop0): __ext4_new_inode:919: comm syz-executor.0: reserved inode found cleared - inode=1
==================================================================
BUG: KASAN: use-after-free in ext4_xattr_set_entry+0x18ab/0x3500 fs/ext4/xattr.c:1747
Write of size 4105 at addr ffff8881675ef5f4 by task syz-executor.0/7092

CPU: 1 PID: 7092 Comm: syz-executor.0 Not tainted 4.19.90-dirty #17
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0xcc/0x11e lib/dump_stack.c:118
 print_address_description.cold.3+0x9/0x223 mm/kasan/report.c:253
 kasan_report_error mm/kasan/report.c:351 [inline]
 kasan_report mm/kasan/report.c:409 [inline]
 kasan_report.cold.4+0x66/0x9d mm/kasan/report.c:393
 memcpy+0x34/0x50 mm/kasan/kasan.c:303
 ext4_xattr_set_entry+0x18ab/0x3500 fs/ext4/xattr.c:1747
 ext4_xattr_ibody_inline_set+0x86/0x2a0 fs/ext4/xattr.c:2205
 ext4_xattr_set_handle+0x940/0x1300 fs/ext4/xattr.c:2386
 ext4_xattr_set+0x1da/0x300 fs/ext4/xattr.c:2498
 __vfs_setxattr+0x112/0x170 fs/xattr.c:149
 __vfs_setxattr_noperm+0x11b/0x2a0 fs/xattr.c:180
 __vfs_setxattr_locked+0x17b/0x250 fs/xattr.c:238
 vfs_setxattr+0xed/0x270 fs/xattr.c:255
 setxattr+0x235/0x330 fs/xattr.c:520
 path_setxattr+0x176/0x190 fs/xattr.c:539
 __do_sys_lsetxattr fs/xattr.c:561 [inline]
 __se_sys_lsetxattr fs/xattr.c:557 [inline]
 __x64_sys_lsetxattr+0xc2/0x160 fs/xattr.c:557
 do_syscall_64+0xdf/0x530 arch/x86/entry/common.c:298
 entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x459fe9
Code: f7 d8 64 89 02 b8 ff ff ff ff c3 66 0f 1f 44 00 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 b4 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fa5e54b4c08 EFLAGS: 00000246 ORIG_RAX: 00000000000000bd
RAX: ffffffffffffffda RBX: 000000000051bf60 RCX: 0000000000459fe9
RDX: 00000000200003c0 RSI: 0000000020000180 RDI: 0000000020000140
RBP: 000000000051bf60 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000001009 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc73c93fc0 R14: 000000000051bf60 R15: 00007fa5e54b4d80

The buggy address belongs to the page:
page:ffffea00059d7bc0 count:0 mapcount:0 mapping:0000000000000000 index:0x1
flags: 0x2fffff80000000()
raw: 002fffff80000000 ffffea00059f3788 ffffea0004c26f08 0000000000000000
raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff8881675ef480: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff8881675ef500: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff8881675ef580: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff

^
 ffff8881675ef600: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff8881675ef680: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================
EXT4-fs error (device loop0): ext4_xattr_ibody_find:2182: inode #2: comm syz-executor.0: corrupted in-inode xattr
capability: warning: `syz-executor.2' uses deprecated v2 capabilities in a way that may be insecure
EXT4-fs error (device loop0): ext4_xattr_ibody_find:2182: inode #2: comm syz-executor.0: corrupted in-inode xattr
VFS: Open an write opened block device exclusively loop2 [7096 syz-executor.2].
EXT4-fs error (device loop0): ext4_xattr_ibody_find:2182: inode #2: comm syz-executor.0: corrupted in-inode xattr
EXT4-fs error (device loop0): ext4_xattr_ibody_find:2182: inode #2: comm syz-executor.0: corrupted in-inode xattr
EXT4-fs error (device loop0): ext4_xattr_ibody_find:2182: inode #2: comm syz-executor.0: corrupted in-inode xattr
```

GVP openEuler/kernel

内容风险标识

评论 (4)

GVPopenEuler/kernel

内容风险标识