[OLK5.10] KASAN: use-after-free Read in lock_get_status

**【标题描述】能够简要描述问题：说明什么场景下，做了什么操作，出现什么问题（尽量使用正向表达方式）**

设置filelock和删除文件并发, 可能出现uaf问题.

**一、缺陷信息**
==================================================================
BUG: KASAN: use-after-free in file_inode include/linux/fs.h:1277 [inline]
BUG: KASAN: use-after-free in lock_get_status+0x713/0x760 fs/locks.c:2635
Read of size 8 at addr ffff888105f9b220 by task syz-executor.3/20350

CPU: 1 PID: 20350 Comm: syz-executor.3 Tainted: G                 ---------r-  - 4.18.0+ #23
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+0x125/0x1ae lib/dump_stack.c:117
 print_address_description+0x70/0x360 mm/kasan/report.c:259
 kasan_report_error mm/kasan/report.c:357 [inline]
 kasan_report+0x1b2/0x340 mm/kasan/report.c:415
 file_inode include/linux/fs.h:1277 [inline]
 lock_get_status+0x713/0x760 fs/locks.c:2635
 locks_show+0x145/0x230 fs/locks.c:2710
 seq_read+0x376/0x12a0 fs/seq_file.c:243
 proc_reg_read+0x104/0x1a0 fs/proc/inode.c:229
 do_loop_readv_writev fs/read_write.c:700 [inline]
 do_iter_read+0x3f4/0x5e0 fs/read_write.c:921
 vfs_readv+0x108/0x180 fs/read_write.c:983
 do_preadv+0x116/0x1a0 fs/read_write.c:1067
 do_syscall_64+0xca/0x5c0 arch/x86/entry/common.c:299
 entry_SYSCALL_64_after_hwframe+0x6a/0xdf
RIP: 0033:0x46bce9
Code: 5d db fa ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 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 0f 83 2b db fa ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f5938ac8c48 EFLAGS: 00000246 ORIG_RAX: 0000000000000127
RAX: ffffffffffffffda RBX: 000000000077bf80 RCX: 000000000046bce9
RDX: 0000000000000001 RSI: 0000000020000140 RDI: 0000000000000004
RBP: 000000000077bf80 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fff2dcb6fdf R14: 00007f5938ac99c0 R15: 00007fff2dcb7170

Allocated by task 20250:
 set_track mm/kasan/kasan.c:463 [inline]
 kasan_kmalloc+0xa0/0xd0 mm/kasan/kasan.c:556
 slab_post_alloc_hook mm/slab.h:516 [inline]
 slab_alloc_node mm/slub.c:2739 [inline]
 slab_alloc mm/slub.c:2747 [inline]
 kmem_cache_alloc+0xde/0x310 mm/slub.c:2752
 kmem_cache_zalloc include/linux/slab.h:739 [inline]
 __alloc_file+0x2f/0x2c0 fs/file_table.c:100
 alloc_empty_file+0x50/0x140 fs/file_table.c:150
 alloc_file+0x83/0x4c0 fs/file_table.c:192
 anon_inode_getfile+0x189/0x2f0 fs/anon_inodes.c:105
 __do_sys_perf_event_open+0xc43/0x2370 kernel/events/core.c:10948
 do_syscall_64+0xca/0x5c0 arch/x86/entry/common.c:299
 entry_SYSCALL_64_after_hwframe+0x6a/0xdf

Freed by task 17:
 set_track mm/kasan/kasan.c:463 [inline]
 __kasan_slab_free+0x130/0x180 mm/kasan/kasan.c:524
 slab_free_hook mm/slub.c:1391 [inline]
 slab_free_freelist_hook mm/slub.c:1419 [inline]
 slab_free mm/slub.c:2986 [inline]
 kmem_cache_free+0xb7/0x350 mm/slub.c:3002
 __rcu_reclaim kernel/rcu/rcu.h:240 [inline]
 rcu_do_batch kernel/rcu/tree.c:2447 [inline]
 invoke_rcu_callbacks kernel/rcu/tree.c:2726 [inline]
 rcu_process_callbacks+0x6b5/0x12b0 kernel/rcu/tree.c:2707
 __do_softirq+0x277/0xc14 kernel/softirq.c:292

The buggy address belongs to the object at ffff888105f9b200
 which belongs to the cache filp of size 456
The buggy address is located 32 bytes inside of
 456-byte region [ffff888105f9b200, ffff888105f9b3c8)
The buggy address belongs to the page:
page:ffffea000417e600 count:1 mapcount:0 mapping:ffff888100180840 index:0x0 compound_mapcount: 0
flags: 0x17ffffc0008100(slab|head)
raw: 0017ffffc0008100 ffffea0004139e00 0000000600000006 ffff888100180840
raw: 0000000000000000 0000000000190019 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff888105f9b100: fb fb fb fb fb fb fb fb fb fc fc fc fc fc fc fc
 ffff888105f9b180: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
>ffff888105f9b200: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
                               ^
 ffff888105f9b280: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
 ffff888105f9b300: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================
**内核信息：**

**缺陷归属组件：**

**缺陷归属的版本：**

**缺陷简述：**

**【环境信息】**
硬件信息
- 裸机场景请提供问题的硬件信息
- 虚拟机场景请提供虚拟机的XML文件或配置信息
软件信息
- OS版本及分支信息
- 内核信息
- 发现问题的组件版本信息
网络信息
- 如果有特殊组网，请提供网络拓扑信息

**【问题复现步骤】**，请描述具体的操作步骤
**【实际结果】**，请描述出问题的结果和影响
**【其他相关附件信息】**
比如系统message日志/组件日志、dump信息、图片等

**缺陷详情参考链接：**

**缺陷分析指导链接：**
https：xxx

GVP openEuler/kernel
Closed

Content Risk Flag

Comments (1)

GVPopenEuler/kernelClosed

Content Risk Flag