登录
注册
开源
企业版
高校版
搜索
帮助中心
使用条款
关于我们
开源
企业版
高校版
私有云
模力方舟
AI 队友
登录
注册
代码拉取完成,页面将自动刷新
开源项目
>
其他开源
>
操作系统
&&
捐赠
捐赠前请先登录
取消
前往登录
扫描微信二维码支付
取消
支付完成
支付提示
将跳转至支付宝完成支付
确定
取消
Watch
不关注
关注所有动态
仅关注版本发行动态
关注但不提醒动态
114
Star
72
Fork
324
src-openEuler
/
kernel
代码
Issues
1057
Pull Requests
39
Wiki
统计
流水线
服务
JavaDoc
PHPDoc
质量分析
Jenkins for Gitee
腾讯云托管
腾讯云 Serverless
悬镜安全
阿里云 SAE
Codeblitz
SBOM
我知道了,不再自动展开
更新失败,请稍后重试!
移除标识
内容风险标识
本任务被
标识为内容中包含有代码安全 Bug 、隐私泄露等敏感信息,仓库外成员不可访问
CVE-2023-52707
已完成
#I9R4N7
CVE和安全问题
openeuler-ci-bot
拥有者
创建于
2024-05-22 03:05
一、漏洞信息 漏洞编号:[CVE-2023-52707](https://nvd.nist.gov/vuln/detail/CVE-2023-52707) 漏洞归属组件:[kernel](https://gitee.com/src-openeuler/kernel) 漏洞归属的版本:4.19.140,4.19.194,4.19.90,5.10.0,6.1.0,6.1.14,6.1.19,6.1.5,6.1.6,6.1.8,6.4.0,6.6.0 CVSS V3.0分值: BaseScore:0.0 None Vector:CVSS:3.0/ 漏洞简述: In the Linux kernel, the following vulnerability has been resolved:sched/psi: Fix use-after-free in ep_remove_wait_queue()If a non-root cgroup gets removed when there is a thread that registeredtrigger and is polling on a pressure file within the cgroup, the pollingwaitqueue gets freed in the following path: do_rmdir cgroup_rmdir kernfs_drain_open_files cgroup_file_release cgroup_pressure_release psi_trigger_destroyHowever, the polling thread still has a reference to the pressure file andwill access the freed waitqueue when the file is closed or upon exit: fput ep_eventpoll_release ep_free ep_remove_wait_queue remove_wait_queueThis results in use-after-free as pasted below.The fundamental problem here is that cgroup_file_release() (andconsequently waitqueue s lifetime) is not tied to the file s real lifetime.Using wake_up_pollfree() here might be less than ideal, but it is in linewith the comment at commit 42288cb44c4b ( wait: add wake_up_pollfree() )since the waitqueue s lifetime is not tied to file s one and can beconsidered as another special case. While this would be fixable by somehowmaking cgroup_file_release() be tied to the fput(), it would requiresizable refactoring at cgroups or higher layer which might be morejustifiable if we identify more cases like this. BUG: KASAN: use-after-free in _raw_spin_lock_irqsave+0x60/0xc0 Write of size 4 at addr ffff88810e625328 by task a.out/4404 CPU: 19 PID: 4404 Comm: a.out Not tainted 6.2.0-rc6 #38 Hardware name: Amazon EC2 c5a.8xlarge/, BIOS 1.0 10/16/2017 Call Trace: <TASK> dump_stack_lvl+0x73/0xa0 print_report+0x16c/0x4e0 kasan_report+0xc3/0xf0 kasan_check_range+0x2d2/0x310 _raw_spin_lock_irqsave+0x60/0xc0 remove_wait_queue+0x1a/0xa0 ep_free+0x12c/0x170 ep_eventpoll_release+0x26/0x30 __fput+0x202/0x400 task_work_run+0x11d/0x170 do_exit+0x495/0x1130 do_group_exit+0x100/0x100 get_signal+0xd67/0xde0 arch_do_signal_or_restart+0x2a/0x2b0 exit_to_user_mode_prepare+0x94/0x100 syscall_exit_to_user_mode+0x20/0x40 do_syscall_64+0x52/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd </TASK> Allocated by task 4404: kasan_set_track+0x3d/0x60 __kasan_kmalloc+0x85/0x90 psi_trigger_create+0x113/0x3e0 pressure_write+0x146/0x2e0 cgroup_file_write+0x11c/0x250 kernfs_fop_write_iter+0x186/0x220 vfs_write+0x3d8/0x5c0 ksys_write+0x90/0x110 do_syscall_64+0x43/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd Freed by task 4407: kasan_set_track+0x3d/0x60 kasan_save_free_info+0x27/0x40 ____kasan_slab_free+0x11d/0x170 slab_free_freelist_hook+0x87/0x150 __kmem_cache_free+0xcb/0x180 psi_trigger_destroy+0x2e8/0x310 cgroup_file_release+0x4f/0xb0 kernfs_drain_open_files+0x165/0x1f0 kernfs_drain+0x162/0x1a0 __kernfs_remove+0x1fb/0x310 kernfs_remove_by_name_ns+0x95/0xe0 cgroup_addrm_files+0x67f/0x700 cgroup_destroy_locked+0x283/0x3c0 cgroup_rmdir+0x29/0x100 kernfs_iop_rmdir+0xd1/0x140 vfs_rmdir+0xfe/0x240 do_rmdir+0x13d/0x280 __x64_sys_rmdir+0x2c/0x30 do_syscall_64+0x43/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd 漏洞公开时间:2024-05-22 00:15:12 漏洞创建时间:2024-05-21 19:05:49 漏洞详情参考链接: https://nvd.nist.gov/vuln/detail/CVE-2023-52707 <details> <summary>更多参考(点击展开)</summary> | 参考来源 | 参考链接 | 来源链接 | | ------- | -------- | -------- | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/7caeb5457bd01ccba0df1d6f4872f20d28e50b38 | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/c2dbe32d5db5c4ead121cf86dabd5ab691fb47fe | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/c6879a4dcefe92d870ab68cabaa9caeda4f2af5a | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/cca2b3feb70170ef6f0fbc4b4d91eea235a2b73a | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/ec9c7aa08819f976b2492fa63c41b5712d2924b5 | | | suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-52707 | https://bugzilla.suse.com/show_bug.cgi?id=1225109 | | suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2023/CVE-2023-52707.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1225109 | | suse_bugzilla | https://git.kernel.org/stable/c/7caeb5457bd01ccba0df1d6f4872f20d28e50b38 | https://bugzilla.suse.com/show_bug.cgi?id=1225109 | | suse_bugzilla | https://git.kernel.org/stable/c/ec9c7aa08819f976b2492fa63c41b5712d2924b5 | https://bugzilla.suse.com/show_bug.cgi?id=1225109 | | suse_bugzilla | https://git.kernel.org/stable/c/cca2b3feb70170ef6f0fbc4b4d91eea235a2b73a | https://bugzilla.suse.com/show_bug.cgi?id=1225109 | | suse_bugzilla | https://git.kernel.org/stable/c/c6879a4dcefe92d870ab68cabaa9caeda4f2af5a | https://bugzilla.suse.com/show_bug.cgi?id=1225109 | | suse_bugzilla | https://git.kernel.org/stable/c/c2dbe32d5db5c4ead121cf86dabd5ab691fb47fe | https://bugzilla.suse.com/show_bug.cgi?id=1225109 | | suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2023-52707 | https://bugzilla.suse.com/show_bug.cgi?id=1225109 | | suse_bugzilla | https://bugzilla.redhat.com/show_bug.cgi?id=2282615 | https://bugzilla.suse.com/show_bug.cgi?id=1225109 | | redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024052158-CVE-2023-52707-e048@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2282615 | | redhat_bugzilla | https://access.redhat.com/errata/RHSA-2024:4823 | https://bugzilla.redhat.com/show_bug.cgi?id=2282615 | | redhat_bugzilla | https://access.redhat.com/errata/RHSA-2024:4831 | https://bugzilla.redhat.com/show_bug.cgi?id=2282615 | | redhat_bugzilla | https://access.redhat.com/errata/RHSA-2024:5102 | https://bugzilla.redhat.com/show_bug.cgi?id=2282615 | | redhat_bugzilla | https://access.redhat.com/errata/RHSA-2024:5101 | https://bugzilla.redhat.com/show_bug.cgi?id=2282615 | | ubuntu | https://www.cve.org/CVERecord?id=CVE-2023-52707 | https://ubuntu.com/security/CVE-2023-52707 | | ubuntu | https://git.kernel.org/linus/c2dbe32d5db5c4ead121cf86dabd5ab691fb47fe (6.2) | https://ubuntu.com/security/CVE-2023-52707 | | ubuntu | https://git.kernel.org/stable/c/7caeb5457bd01ccba0df1d6f4872f20d28e50b38 | https://ubuntu.com/security/CVE-2023-52707 | | ubuntu | https://git.kernel.org/stable/c/ec9c7aa08819f976b2492fa63c41b5712d2924b5 | https://ubuntu.com/security/CVE-2023-52707 | | ubuntu | https://git.kernel.org/stable/c/cca2b3feb70170ef6f0fbc4b4d91eea235a2b73a | https://ubuntu.com/security/CVE-2023-52707 | | ubuntu | https://git.kernel.org/stable/c/c6879a4dcefe92d870ab68cabaa9caeda4f2af5a | https://ubuntu.com/security/CVE-2023-52707 | | ubuntu | https://git.kernel.org/stable/c/c2dbe32d5db5c4ead121cf86dabd5ab691fb47fe | https://ubuntu.com/security/CVE-2023-52707 | | ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2023-52707 | https://ubuntu.com/security/CVE-2023-52707 | | ubuntu | https://launchpad.net/bugs/cve/CVE-2023-52707 | https://ubuntu.com/security/CVE-2023-52707 | | ubuntu | https://security-tracker.debian.org/tracker/CVE-2023-52707 | https://ubuntu.com/security/CVE-2023-52707 | | debian | | https://security-tracker.debian.org/tracker/CVE-2023-52707 | | anolis | | https://anas.openanolis.cn/cves/detail/CVE-2023-52707 | </details> 漏洞分析指导链接: https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md 漏洞数据来源: openBrain开源漏洞感知系统 漏洞补丁信息: <details> <summary>详情(点击展开)</summary> | 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源 | | ------- | -------- | ------- | -------- | --------- | | linux | | https://git.kernel.org/linus/c2dbe32d5db5c4ead121cf86dabd5ab691fb47fe | https://git.kernel.org/linus/0e94682b73bfa6c44c98af7a26771c9c08c055d5 | ubuntu | </details> 二、漏洞分析结构反馈 影响性分析说明: In the Linux kernel, the following vulnerability has been resolved:sched/psi: Fix use-after-free in ep_remove_wait_queue()If a non-root cgroup gets removed when there is a thread that registeredtrigger and is polling on a pressure file within the cgroup, the pollingwaitqueue gets freed in the following path: do_rmdir cgroup_rmdir kernfs_drain_open_files cgroup_file_release cgroup_pressure_release psi_trigger_destroyHowever, the polling thread still has a reference to the pressure file andwill access the freed waitqueue when the file is closed or upon exit: fput ep_eventpoll_release ep_free ep_remove_wait_queue remove_wait_queueThis results in use-after-free as pasted below.The fundamental problem here is that cgroup_file_release() (andconsequently waitqueue s lifetime) is not tied to the file s real lifetime.Using wake_up_pollfree() here might be less than ideal, but it is in linewith the comment at commit 42288cb44c4b ( wait: add wake_up_pollfree() )since the waitqueue s lifetime is not tied to file s one and can beconsidered as another special case. While this would be fixable by somehowmaking cgroup_file_release() be tied to the fput(), it would requiresizable refactoring at cgroups or higher layer which might be morejustifiable if we identify more cases like this. BUG: KASAN: use-after-free in _raw_spin_lock_irqsave+0x60/0xc0 Write of size 4 at addr ffff88810e625328 by task a.out/4404CPU: 19 PID: 4404 Comm: a.out Not tainted 6.2.0-rc6 #38Hardware name: Amazon EC2 c5a.8xlarge/, BIOS 1.0 10/16/2017Call Trace:<TASK>dump_stack_lvl+0x73/0xa0print_report+0x16c/0x4e0kasan_report+0xc3/0xf0kasan_check_range+0x2d2/0x310_raw_spin_lock_irqsave+0x60/0xc0remove_wait_queue+0x1a/0xa0ep_free+0x12c/0x170ep_eventpoll_release+0x26/0x30__fput+0x202/0x400task_work_run+0x11d/0x170do_exit+0x495/0x1130do_group_exit+0x100/0x100get_signal+0xd67/0xde0arch_do_signal_or_restart+0x2a/0x2b0exit_to_user_mode_prepare+0x94/0x100syscall_exit_to_user_mode+0x20/0x40do_syscall_64+0x52/0x90entry_SYSCALL_64_after_hwframe+0x63/0xcd</TASK> Allocated by task 4404:kasan_set_track+0x3d/0x60__kasan_kmalloc+0x85/0x90psi_trigger_create+0x113/0x3e0pressure_write+0x146/0x2e0cgroup_file_write+0x11c/0x250kernfs_fop_write_iter+0x186/0x220vfs_write+0x3d8/0x5c0ksys_write+0x90/0x110do_syscall_64+0x43/0x90entry_SYSCALL_64_after_hwframe+0x63/0xcd Freed by task 4407:kasan_set_track+0x3d/0x60kasan_save_free_info+0x27/0x40____kasan_slab_free+0x11d/0x170slab_free_freelist_hook+0x87/0x150__kmem_cache_free+0xcb/0x180psi_trigger_destroy+0x2e8/0x310cgroup_file_release+0x4f/0xb0kernfs_drain_open_files+0x165/0x1f0kernfs_drain+0x162/0x1a0__kernfs_remove+0x1fb/0x310kernfs_remove_by_name_ns+0x95/0xe0cgroup_addrm_files+0x67f/0x700cgroup_destroy_locked+0x283/0x3c0cgroup_rmdir+0x29/0x100kernfs_iop_rmdir+0xd1/0x140vfs_rmdir+0xfe/0x240do_rmdir+0x13d/0x280__x64_sys_rmdir+0x2c/0x30do_syscall_64+0x43/0x90entry_SYSCALL_64_after_hwframe+0x63/0xcd openEuler评分: 7.8 Vector:CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H 受影响版本排查(受影响/不受影响): 1.openEuler-22.03-LTS-SP1(5.10.0):受影响 2.openEuler-20.03-LTS-SP4(4.19.90):不受影响 3.openEuler-22.03-LTS-SP3(5.10.0):不受影响 4.openEuler-22.03-LTS-SP4(5.10.0):不受影响 5.master(6.6.0):不受影响 6.openEuler-24.03-LTS(6.6.0):不受影响 7.openEuler-24.03-LTS-Next(6.6.0):不受影响 修复是否涉及abi变化(是/否): 1.openEuler-20.03-LTS-SP4(4.19.90):否 2.openEuler-22.03-LTS-SP1(5.10.0):否 3.openEuler-22.03-LTS-SP3(5.10.0):否 4.master(6.6.0):否 5.openEuler-24.03-LTS(6.6.0):否 6.openEuler-24.03-LTS-Next(6.6.0):否 7.openEuler-22.03-LTS-SP4(5.10.0):否 三、漏洞修复 安全公告链接:https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2024-2257
一、漏洞信息 漏洞编号:[CVE-2023-52707](https://nvd.nist.gov/vuln/detail/CVE-2023-52707) 漏洞归属组件:[kernel](https://gitee.com/src-openeuler/kernel) 漏洞归属的版本:4.19.140,4.19.194,4.19.90,5.10.0,6.1.0,6.1.14,6.1.19,6.1.5,6.1.6,6.1.8,6.4.0,6.6.0 CVSS V3.0分值: BaseScore:0.0 None Vector:CVSS:3.0/ 漏洞简述: In the Linux kernel, the following vulnerability has been resolved:sched/psi: Fix use-after-free in ep_remove_wait_queue()If a non-root cgroup gets removed when there is a thread that registeredtrigger and is polling on a pressure file within the cgroup, the pollingwaitqueue gets freed in the following path: do_rmdir cgroup_rmdir kernfs_drain_open_files cgroup_file_release cgroup_pressure_release psi_trigger_destroyHowever, the polling thread still has a reference to the pressure file andwill access the freed waitqueue when the file is closed or upon exit: fput ep_eventpoll_release ep_free ep_remove_wait_queue remove_wait_queueThis results in use-after-free as pasted below.The fundamental problem here is that cgroup_file_release() (andconsequently waitqueue s lifetime) is not tied to the file s real lifetime.Using wake_up_pollfree() here might be less than ideal, but it is in linewith the comment at commit 42288cb44c4b ( wait: add wake_up_pollfree() )since the waitqueue s lifetime is not tied to file s one and can beconsidered as another special case. While this would be fixable by somehowmaking cgroup_file_release() be tied to the fput(), it would requiresizable refactoring at cgroups or higher layer which might be morejustifiable if we identify more cases like this. BUG: KASAN: use-after-free in _raw_spin_lock_irqsave+0x60/0xc0 Write of size 4 at addr ffff88810e625328 by task a.out/4404 CPU: 19 PID: 4404 Comm: a.out Not tainted 6.2.0-rc6 #38 Hardware name: Amazon EC2 c5a.8xlarge/, BIOS 1.0 10/16/2017 Call Trace: <TASK> dump_stack_lvl+0x73/0xa0 print_report+0x16c/0x4e0 kasan_report+0xc3/0xf0 kasan_check_range+0x2d2/0x310 _raw_spin_lock_irqsave+0x60/0xc0 remove_wait_queue+0x1a/0xa0 ep_free+0x12c/0x170 ep_eventpoll_release+0x26/0x30 __fput+0x202/0x400 task_work_run+0x11d/0x170 do_exit+0x495/0x1130 do_group_exit+0x100/0x100 get_signal+0xd67/0xde0 arch_do_signal_or_restart+0x2a/0x2b0 exit_to_user_mode_prepare+0x94/0x100 syscall_exit_to_user_mode+0x20/0x40 do_syscall_64+0x52/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd </TASK> Allocated by task 4404: kasan_set_track+0x3d/0x60 __kasan_kmalloc+0x85/0x90 psi_trigger_create+0x113/0x3e0 pressure_write+0x146/0x2e0 cgroup_file_write+0x11c/0x250 kernfs_fop_write_iter+0x186/0x220 vfs_write+0x3d8/0x5c0 ksys_write+0x90/0x110 do_syscall_64+0x43/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd Freed by task 4407: kasan_set_track+0x3d/0x60 kasan_save_free_info+0x27/0x40 ____kasan_slab_free+0x11d/0x170 slab_free_freelist_hook+0x87/0x150 __kmem_cache_free+0xcb/0x180 psi_trigger_destroy+0x2e8/0x310 cgroup_file_release+0x4f/0xb0 kernfs_drain_open_files+0x165/0x1f0 kernfs_drain+0x162/0x1a0 __kernfs_remove+0x1fb/0x310 kernfs_remove_by_name_ns+0x95/0xe0 cgroup_addrm_files+0x67f/0x700 cgroup_destroy_locked+0x283/0x3c0 cgroup_rmdir+0x29/0x100 kernfs_iop_rmdir+0xd1/0x140 vfs_rmdir+0xfe/0x240 do_rmdir+0x13d/0x280 __x64_sys_rmdir+0x2c/0x30 do_syscall_64+0x43/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd 漏洞公开时间:2024-05-22 00:15:12 漏洞创建时间:2024-05-21 19:05:49 漏洞详情参考链接: https://nvd.nist.gov/vuln/detail/CVE-2023-52707 <details> <summary>更多参考(点击展开)</summary> | 参考来源 | 参考链接 | 来源链接 | | ------- | -------- | -------- | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/7caeb5457bd01ccba0df1d6f4872f20d28e50b38 | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/c2dbe32d5db5c4ead121cf86dabd5ab691fb47fe | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/c6879a4dcefe92d870ab68cabaa9caeda4f2af5a | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/cca2b3feb70170ef6f0fbc4b4d91eea235a2b73a | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/ec9c7aa08819f976b2492fa63c41b5712d2924b5 | | | suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-52707 | https://bugzilla.suse.com/show_bug.cgi?id=1225109 | | suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2023/CVE-2023-52707.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1225109 | | suse_bugzilla | https://git.kernel.org/stable/c/7caeb5457bd01ccba0df1d6f4872f20d28e50b38 | https://bugzilla.suse.com/show_bug.cgi?id=1225109 | | suse_bugzilla | https://git.kernel.org/stable/c/ec9c7aa08819f976b2492fa63c41b5712d2924b5 | https://bugzilla.suse.com/show_bug.cgi?id=1225109 | | suse_bugzilla | https://git.kernel.org/stable/c/cca2b3feb70170ef6f0fbc4b4d91eea235a2b73a | https://bugzilla.suse.com/show_bug.cgi?id=1225109 | | suse_bugzilla | https://git.kernel.org/stable/c/c6879a4dcefe92d870ab68cabaa9caeda4f2af5a | https://bugzilla.suse.com/show_bug.cgi?id=1225109 | | suse_bugzilla | https://git.kernel.org/stable/c/c2dbe32d5db5c4ead121cf86dabd5ab691fb47fe | https://bugzilla.suse.com/show_bug.cgi?id=1225109 | | suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2023-52707 | https://bugzilla.suse.com/show_bug.cgi?id=1225109 | | suse_bugzilla | https://bugzilla.redhat.com/show_bug.cgi?id=2282615 | https://bugzilla.suse.com/show_bug.cgi?id=1225109 | | redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024052158-CVE-2023-52707-e048@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2282615 | | redhat_bugzilla | https://access.redhat.com/errata/RHSA-2024:4823 | https://bugzilla.redhat.com/show_bug.cgi?id=2282615 | | redhat_bugzilla | https://access.redhat.com/errata/RHSA-2024:4831 | https://bugzilla.redhat.com/show_bug.cgi?id=2282615 | | redhat_bugzilla | https://access.redhat.com/errata/RHSA-2024:5102 | https://bugzilla.redhat.com/show_bug.cgi?id=2282615 | | redhat_bugzilla | https://access.redhat.com/errata/RHSA-2024:5101 | https://bugzilla.redhat.com/show_bug.cgi?id=2282615 | | ubuntu | https://www.cve.org/CVERecord?id=CVE-2023-52707 | https://ubuntu.com/security/CVE-2023-52707 | | ubuntu | https://git.kernel.org/linus/c2dbe32d5db5c4ead121cf86dabd5ab691fb47fe (6.2) | https://ubuntu.com/security/CVE-2023-52707 | | ubuntu | https://git.kernel.org/stable/c/7caeb5457bd01ccba0df1d6f4872f20d28e50b38 | https://ubuntu.com/security/CVE-2023-52707 | | ubuntu | https://git.kernel.org/stable/c/ec9c7aa08819f976b2492fa63c41b5712d2924b5 | https://ubuntu.com/security/CVE-2023-52707 | | ubuntu | https://git.kernel.org/stable/c/cca2b3feb70170ef6f0fbc4b4d91eea235a2b73a | https://ubuntu.com/security/CVE-2023-52707 | | ubuntu | https://git.kernel.org/stable/c/c6879a4dcefe92d870ab68cabaa9caeda4f2af5a | https://ubuntu.com/security/CVE-2023-52707 | | ubuntu | https://git.kernel.org/stable/c/c2dbe32d5db5c4ead121cf86dabd5ab691fb47fe | https://ubuntu.com/security/CVE-2023-52707 | | ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2023-52707 | https://ubuntu.com/security/CVE-2023-52707 | | ubuntu | https://launchpad.net/bugs/cve/CVE-2023-52707 | https://ubuntu.com/security/CVE-2023-52707 | | ubuntu | https://security-tracker.debian.org/tracker/CVE-2023-52707 | https://ubuntu.com/security/CVE-2023-52707 | | debian | | https://security-tracker.debian.org/tracker/CVE-2023-52707 | | anolis | | https://anas.openanolis.cn/cves/detail/CVE-2023-52707 | </details> 漏洞分析指导链接: https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md 漏洞数据来源: openBrain开源漏洞感知系统 漏洞补丁信息: <details> <summary>详情(点击展开)</summary> | 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源 | | ------- | -------- | ------- | -------- | --------- | | linux | | https://git.kernel.org/linus/c2dbe32d5db5c4ead121cf86dabd5ab691fb47fe | https://git.kernel.org/linus/0e94682b73bfa6c44c98af7a26771c9c08c055d5 | ubuntu | </details> 二、漏洞分析结构反馈 影响性分析说明: In the Linux kernel, the following vulnerability has been resolved:sched/psi: Fix use-after-free in ep_remove_wait_queue()If a non-root cgroup gets removed when there is a thread that registeredtrigger and is polling on a pressure file within the cgroup, the pollingwaitqueue gets freed in the following path: do_rmdir cgroup_rmdir kernfs_drain_open_files cgroup_file_release cgroup_pressure_release psi_trigger_destroyHowever, the polling thread still has a reference to the pressure file andwill access the freed waitqueue when the file is closed or upon exit: fput ep_eventpoll_release ep_free ep_remove_wait_queue remove_wait_queueThis results in use-after-free as pasted below.The fundamental problem here is that cgroup_file_release() (andconsequently waitqueue s lifetime) is not tied to the file s real lifetime.Using wake_up_pollfree() here might be less than ideal, but it is in linewith the comment at commit 42288cb44c4b ( wait: add wake_up_pollfree() )since the waitqueue s lifetime is not tied to file s one and can beconsidered as another special case. While this would be fixable by somehowmaking cgroup_file_release() be tied to the fput(), it would requiresizable refactoring at cgroups or higher layer which might be morejustifiable if we identify more cases like this. BUG: KASAN: use-after-free in _raw_spin_lock_irqsave+0x60/0xc0 Write of size 4 at addr ffff88810e625328 by task a.out/4404CPU: 19 PID: 4404 Comm: a.out Not tainted 6.2.0-rc6 #38Hardware name: Amazon EC2 c5a.8xlarge/, BIOS 1.0 10/16/2017Call Trace:<TASK>dump_stack_lvl+0x73/0xa0print_report+0x16c/0x4e0kasan_report+0xc3/0xf0kasan_check_range+0x2d2/0x310_raw_spin_lock_irqsave+0x60/0xc0remove_wait_queue+0x1a/0xa0ep_free+0x12c/0x170ep_eventpoll_release+0x26/0x30__fput+0x202/0x400task_work_run+0x11d/0x170do_exit+0x495/0x1130do_group_exit+0x100/0x100get_signal+0xd67/0xde0arch_do_signal_or_restart+0x2a/0x2b0exit_to_user_mode_prepare+0x94/0x100syscall_exit_to_user_mode+0x20/0x40do_syscall_64+0x52/0x90entry_SYSCALL_64_after_hwframe+0x63/0xcd</TASK> Allocated by task 4404:kasan_set_track+0x3d/0x60__kasan_kmalloc+0x85/0x90psi_trigger_create+0x113/0x3e0pressure_write+0x146/0x2e0cgroup_file_write+0x11c/0x250kernfs_fop_write_iter+0x186/0x220vfs_write+0x3d8/0x5c0ksys_write+0x90/0x110do_syscall_64+0x43/0x90entry_SYSCALL_64_after_hwframe+0x63/0xcd Freed by task 4407:kasan_set_track+0x3d/0x60kasan_save_free_info+0x27/0x40____kasan_slab_free+0x11d/0x170slab_free_freelist_hook+0x87/0x150__kmem_cache_free+0xcb/0x180psi_trigger_destroy+0x2e8/0x310cgroup_file_release+0x4f/0xb0kernfs_drain_open_files+0x165/0x1f0kernfs_drain+0x162/0x1a0__kernfs_remove+0x1fb/0x310kernfs_remove_by_name_ns+0x95/0xe0cgroup_addrm_files+0x67f/0x700cgroup_destroy_locked+0x283/0x3c0cgroup_rmdir+0x29/0x100kernfs_iop_rmdir+0xd1/0x140vfs_rmdir+0xfe/0x240do_rmdir+0x13d/0x280__x64_sys_rmdir+0x2c/0x30do_syscall_64+0x43/0x90entry_SYSCALL_64_after_hwframe+0x63/0xcd openEuler评分: 7.8 Vector:CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H 受影响版本排查(受影响/不受影响): 1.openEuler-22.03-LTS-SP1(5.10.0):受影响 2.openEuler-20.03-LTS-SP4(4.19.90):不受影响 3.openEuler-22.03-LTS-SP3(5.10.0):不受影响 4.openEuler-22.03-LTS-SP4(5.10.0):不受影响 5.master(6.6.0):不受影响 6.openEuler-24.03-LTS(6.6.0):不受影响 7.openEuler-24.03-LTS-Next(6.6.0):不受影响 修复是否涉及abi变化(是/否): 1.openEuler-20.03-LTS-SP4(4.19.90):否 2.openEuler-22.03-LTS-SP1(5.10.0):否 3.openEuler-22.03-LTS-SP3(5.10.0):否 4.master(6.6.0):否 5.openEuler-24.03-LTS(6.6.0):否 6.openEuler-24.03-LTS-Next(6.6.0):否 7.openEuler-22.03-LTS-SP4(5.10.0):否 三、漏洞修复 安全公告链接:https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2024-2257
评论 (
12
)
登录
后才可以发表评论
状态
已完成
待办的
已挂起
进行中
已完成
已拒绝
负责人
未设置
sanglipeng
sanglipeng
负责人
协作者
+负责人
+协作者
标签
CVE/UNAFFECTED
sig/Kernel
未设置
项目
未立项任务
未立项任务
Pull Requests
未关联
未关联
关联的 Pull Requests 被合并后可能会关闭此 issue
分支
未关联
分支 (38)
标签 (271)
master
openEuler-24.03-LTS-SP3
openEuler-24.03-LTS-SP1
openEuler-24.03-LTS-SP2
openEuler-24.03-LTS
openEuler-22.03-LTS-SP3
openEuler-22.03-LTS-SP4
openEuler-20.03-LTS-SP4
openEuler-25.09
openEuler-24.03-LTS-Next
openEuler-25.03
openEuler-22.03-LTS-SP2
openEuler-22.03-LTS-SP1
openEuler-22.03-LTS-SP4-64KB
openEuler-24.09
openEuler-22.03-LTS-Next
openEuler-24.03-LTS-Loongarch
openEuler-22.03-LTS
openEuler-20.03-LTS-SP1
sync-pr1519-openEuler-24.03-LTS-to-openEuler-24.03-LTS-Next
sync-pr1486-master-to-openEuler-24.03-LTS-Next
loongarch-support
openEuler-20.03-LTS-SP3
sync-pr1314-openEuler-22.03-LTS-SP3-to-openEuler-22.03-LTS-Next
openEuler-23.09
openEuler-23.03
openEuler-22.03-LTS-LoongArch
openEuler-22.09
openEuler-22.09-HeXin
openEuler-20.03-LTS-SP2
openEuler-21.09
openEuler-20.03-LTS
openEuler-20.03-LTS-Next
openEuler-21.03
openEuler-20.09
openEuler-20.03-LTS-SP1-testing
openEuler1.0
openEuler1.0-base
openEuler-24.03-LTS-SP1-update-20251024
openEuler-20.03-LTS-SP4-update-20251024
openEuler-24.03-LTS-update-20251024
openEuler-22.03-LTS-SP3-update-20251024
openEuler-22.03-LTS-SP4-update-20251024
openEuler-24.03-LTS-SP2-update-20251024
openEuler-20.03-LTS-SP4-update-20251017
openEuler-22.03-LTS-SP3-update-20251017
openEuler-24.03-LTS-update-20251017
openEuler-24.03-LTS-SP1-update-20251017
openEuler-24.03-LTS-SP2-update-20251017
openEuler-22.03-LTS-SP4-update-20251017
openEuler-20.03-LTS-SP4-update-20251011
openEuler-22.03-LTS-SP4-update-20251011
openEuler-22.03-LTS-SP3-update-20251011
openEuler-24.03-LTS-update-20250929
openEuler-25.09-release
openEuler-20.03-LTS-SP4-update-20250926
openEuler-24.03-LTS-update-20250926
openEuler-22.03-LTS-SP3-update-20250926
openEuler-22.03-LTS-SP4-update-20250926
openEuler-24.03-LTS-SP1-update-20250926
openEuler-24.03-LTS-SP2-update-20250926
openEuler-20.03-LTS-SP4-update-20250919
openEuler-22.03-LTS-SP3-update-20250919
openEuler-24.03-LTS-update-20250919
openEuler-22.03-LTS-SP4-update-20250919
openEuler-24.03-LTS-SP1-update-20250919
openEuler-24.03-LTS-SP2-update-20250919
openEuler-20.03-LTS-SP4-update-20250912
openEuler-22.03-LTS-SP3-update-20250912
openEuler-22.03-LTS-SP4-update-20250912
openEuler-24.03-LTS-update-20250912
openEuler-24.03-LTS-SP1-update-20250912
openEuler-24.03-LTS-SP2-update-20250912
openEuler-24.03-LTS-SP1-update-20250911
openEuler-24.03-LTS-update-20250905
openEuler-20.03-LTS-SP4-update-20250905
openEuler-22.03-LTS-SP3-update-20250905
openEuler-22.03-LTS-SP4-update-20250905
openEuler-24.03-LTS-SP1-update-20250905
openEuler-24.03-LTS-SP2-update-20250905
openEuler-20.03-LTS-SP4-update-20250829
openEuler-22.03-LTS-SP4-update-20250829
openEuler-24.03-LTS-SP1-update-20250829
openEuler-24.03-LTS-update-20250829
openEuler-24.03-LTS-SP2-update-20250829
openEuler-22.03-LTS-SP3-update-20250822
openEuler-22.03-LTS-SP4-update-20250822
openEuler-24.03-LTS-update-20250822
openEuler-24.03-LTS-SP1-update-20250822
openEuler-24.03-LTS-SP2-update-20250822
openEuler-22.03-LTS-SP4-update-20250815
openEuler-22.03-LTS-SP3-update-20250815
openEuler-24.03-LTS-SP2-update-20250815
openEuler-20.03-LTS-SP4-update-20250815
openEuler-24.03-LTS-update-20250815
openEuler-24.03-LTS-SP1-update-20250815
openEuler-20.03-LTS-SP4-update-20250808
openEuler-22.03-LTS-SP3-update-20250808
openEuler-22.03-LTS-SP4-update-20250808
openEuler-24.03-LTS-update-20250808
openEuler-24.03-LTS-SP1-update-20250808
openEuler-24.03-LTS-SP2-update-20250808
openEuler-22.03-LTS-SP3-update-20250801
openEuler-22.03-LTS-SP4-update-20250801
openEuler-24.03-LTS-update-20250801
openEuler-24.03-LTS-SP1-update-20250801
openEuler-24.03-LTS-SP2-update-20250801
openEuler-20.03-LTS-SP4-update-20250725
openEuler-22.03-LTS-SP3-update-20250725
openEuler-22.03-LTS-SP4-update-20250725
openEuler-24.03-LTS-update-20250725
openEuler-24.03-LTS-SP1-update-20250725
openEuler-24.03-LTS-SP2-update-20250725
openEuler-20.03-LTS-SP4-update-20250718
openEuler-22.03-LTS-SP3-update-20250718
openEuler-22.03-LTS-SP4-update-20250718
openEuler-24.03-LTS-update-20250718
openEuler-24.03-LTS-SP1-update-20250718
openEuler-24.03-LTS-SP2-update-20250718
openEuler-20.03-LTS-SP4-update-20250711
openEuler-22.03-LTS-SP3-update-20250711
openEuler-22.03-LTS-SP4-update-20250711
openEuler-24.03-LTS-update-20250711
openEuler-24.03-LTS-SP1-update-20250711
openEuler-20.03-LTS-SP4-update-20250704
openEuler-22.03-LTS-SP3-update-20250704
openEuler-22.03-LTS-SP4-update-20250704
openEuler-24.03-LTS-update-20250704
openEuler-24.03-LTS-SP1-update-20250704
openEuler-20.03-LTS-SP4-update-20250627
openEuler-22.03-LTS-SP3-update-20250627
openEuler-22.03-LTS-SP4-update-20250627
openEuler-20.03-LTS-SP4-update-20250620
openEuler-22.03-LTS-SP3-update-20250620
openEuler-22.03-LTS-SP4-update-20250620
openEuler-24.03-LTS-update-20250620
openEuler-24.03-LTS-SP1-update-20250620
openEuler-24.03-LTS-SP2-release
openEuler-20.03-LTS-SP4-update-20250613
openEuler-22.03-LTS-SP3-update-20250613
openEuler-22.03-LTS-SP4-update-20250613
openEuler-24.03-LTS-update-20250613
openEuler-24.03-LTS-SP1-update-20250613
openEuler-20.03-LTS-SP4-update-20250606
openEuler-22.03-LTS-SP3-update-20250606
openEuler-22.03-LTS-SP4-update-20250606
openEuler-24.03-LTS-update-20250606
openEuler-24.03-LTS-SP1-update-20250606
openEuler-20.03-LTS-SP4-update-20250530
openEuler-22.03-LTS-SP3-update-20250530
openEuler-22.03-LTS-SP4-update-20250530
openEuler-24.03-LTS-update-20250530
openEuler-24.03-LTS-SP1-update-20250530
openEuler-20.03-LTS-SP4-update-20250523
openEuler-24.03-LTS-update-20250523
openEuler-24.03-LTS-SP1-update-20250523
openEuler-24.03-LTS-SP1-update-20250516
openEuler-24.03-LTS-update-20250516
openEuler-22.03-LTS-SP4-update-20250516
openEuler-22.03-LTS-SP3-update-20250516
openEuler-20.03-LTS-SP4-update-20250516
openEuler-24.03-LTS-SP1-update-20250509
openEuler-24.03-LTS-update-20250509
openEuler-22.03-LTS-SP4-update-20250509
openEuler-22.03-LTS-SP3-update-20250509
openEuler-20.03-LTS-SP4-update-20250509
openEuler-24.03-LTS-update-20250425
openEuler-22.03-LTS-SP3-update-20250425
openEuler-24.03-LTS-SP1-update-20250425
openEuler-24.03-LTS-SP1-update-20250428
openEuler-22.03-LTS-SP4-update-20250425
openEuler-20.03-LTS-SP4-update-20250425
openEuler-22.03-LTS-SP3-update-20250418
openEuler-22.03-LTS-SP4-update-20250418
openEuler-20.03-LTS-SP4-update-20250418
openEuler-22.03-LTS-SP3-update-20250411
openEuler-22.03-LTS-SP4-update-20250411
openEuler-20.03-LTS-SP4-update-20250411
openEuler-20.03-LTS-SP4-update-20250403
openEuler-24.03-LTS-SP1-update-20250403
openEuler-24.03-LTS-update-20250403
openEuler-25.03-release
openEuler-20.03-LTS-SP4-update-20250329
openEuler-22.03-LTS-SP4-update-20250329
openEuler-22.03-LTS-SP3-update-20250329
openEuler-24.03-LTS-SP1-update-20250329
openEuler-24.03-LTS-update-20250329
openEuler-24.03-LTS-update-20250321
openEuler-24.03-LTS-SP1-update-20250321
openEuler-20.03-LTS-SP4-update-20250321
openEuler-24.03-LTS-update-20250314
openEuler-24.03-LTS-SP1-update-20250314
openEuler-22.03-LTS-SP3-update-20250314
openEuler-22.03-LTS-SP4-update-20250314
openEuler-20.03-LTS-SP4-update-20250314
openEuler-24.03-LTS-update-20250307
openEuler-24.03-LTS-SP1-update-20250307
openEuler-22.03-LTS-SP3-update-20250307
openEuler-22.03-LTS-SP4-update-20250307
openEuler-20.03-LTS-SP4-update-20250307
openEuler-24.03-LTS-update-20250228
openEuler-24.03-LTS-SP1-update-20250228
openEuler-22.03-LTS-SP3-update-20250228
openEuler-22.03-LTS-SP4-update-20250228
openEuler-20.03-LTS-SP4-update-20250228
openEuler-24.03-LTS-SP1-update-20250221
openEuler-24.03-LTS-update-20250221
openEuler-22.03-LTS-SP4-update-20250221
openEuler-22.03-LTS-SP3-update-20250221
openEuler-20.03-LTS-SP4-update-20250221
openEuler-24.03-LTS-update-20250214
openEuler-24.03-LTS-SP1-update-20250214
openEuler-22.03-LTS-SP4-update-20250214
openEuler-22.03-LTS-SP3-update-20250214
openEuler-20.03-LTS-SP4-update-20250214
openEuler-24.03-LTS-update-20250208
openEuler-20.03-LTS-SP4-update-20250208
openEuler-22.03-LTS-SP3-update-20250208
openEuler-22.03-LTS-SP4-update-20250208
openEuler-24.03-LTS-SP1-update-20250208
openEuler-24.03-LTS-SP1-update-20250124
openEuler-22.03-LTS-SP4-update-20250124
openEuler-22.03-LTS-SP3-update-20250124
openEuler-20.03-LTS-SP4-update-20250124
openEuler-24.03-LTS-update-20250124
openEuler-22.03-LTS-SP3-update-20250117
openEuler-22.03-LTS-SP4-update-20250117
openEuler-20.03-LTS-SP4-update-20250117
openEuler-24.03-LTS-update-20250110
openEuler-24.03-LTS-SP1-update-20250110
openEuler-22.03-LTS-SP1-update-20250110
openEuler-22.03-LTS-SP3-update-20250110
openEuler-20.03-LTS-SP4-update-20250110
openEuler-22.03-LTS-SP4-update-20250110
openEuler-22.03-LTS-SP4-update-20250103
openEuler-22.03-LTS-SP3-update-20250103
openEuler-22.03-LTS-SP1-update-20250103
openEuler-20.03-LTS-SP4-update-20250103
openEuler-24.03-LTS-SP1-release
openEuler-24.03-LTS-update-20241227
openEuler-22.03-LTS-SP3-update-20241227
openEuler-22.03-LTS-SP4-update-20241227
openEuler-20.03-LTS-SP4-update-20241227
openEuler-22.03-LTS-SP4-update-20241220
openEuler-22.03-LTS-SP3-update-20241220
openEuler-20.03-LTS-SP4-update-20241220
openEuler-24.03-LTS-update-20241213
openEuler-22.03-LTS-SP4-update-20241213
openEuler-22.03-LTS-SP3-update-20241213
openEuler-22.03-LTS-SP1-update-20241213
openEuler-20.03-LTS-SP4-update-20241213
openEuler-24.03-LTS-update-20241206
openEuler-22.03-LTS-SP4-update-20241206
openEuler-22.03-LTS-SP3-update-20241206
openEuler-22.03-LTS-SP1-update-20241206
openEuler-20.03-LTS-SP4-update-20241206
openEuler-20.03-LTS-SP4-update-20241129
openEuler-22.03-LTS-SP1-update-20241129
openEuler-22.03-LTS-SP3-update-20241129
openEuler-22.03-LTS-SP4-update-20241129
openEuler-24.03-LTS-update-20241129
openEuler-24.03-LTS-update-20241122
openEuler-22.03-LTS-SP4-update-20241122
openEuler-22.03-LTS-SP3-update-20241122
openEuler-22.03-LTS-SP1-update-20241122
openEuler-20.03-LTS-SP4-update-20241122
openEuler-20.03-LTS-SP4-update-20241115
openEuler-22.03-LTS-SP1-update-20241115
openEuler-22.03-LTS-SP3-update-20241115
openEuler-22.03-LTS-SP4-update-20241115
openEuler-24.03-LTS-update-20241115
openEuler-24.03-LTS-update-20241108
openEuler-22.03-LTS-SP4-update-20241108
openEuler-22.03-LTS-SP3-update-20241108
openEuler-22.03-LTS-SP1-update-20241108
openEuler-20.03-LTS-SP4-update-20241108
openEuler-22.03-LTS-SP4-update-before-20241025
openEuler-22.03-LTS-SP4-before-20241025
openEuler-24.03-LTS-update-before-20241025
openEuler-20.03-LTS-SP4-update-20241101
openEuler-22.03-LTS-SP1-update-20241101
openEuler-22.03-LTS-SP3-update-20241101
openEuler-22.03-LTS-SP4-update-20241101
openEuler-24.03-LTS-update-20241101
openEuler-20.03-LTS-SP4-update-20241025
openEuler-22.03-LTS-SP1-update-20241025
openEuler-22.03-LTS-SP3-update-20241025
openEuler-22.03-LTS-SP4-update-20241025
openEuler-24.03-LTS-update-20241025
openEuler-22.03-LTS-SP4-release
openEuler-24.09-release
openEuler-24.03-LTS-release
openEuler-22.03-LTS-SP3-release
openEuler-23.09-rc5
openEuler-22.03-LTS-SP1-release
openEuler-22.09-release
openEuler-22.09-rc5
openEuler-22.09-20220829
openEuler-22.03-LTS-20220331
openEuler-22.03-LTS-round5
openEuler-22.03-LTS-round3
openEuler-22.03-LTS-round2
openEuler-22.03-LTS-round1
openEuler-20.03-LTS-SP3-release
openEuler-20.03-LTS-SP2-20210624
openEuler-21.03-20210330
openEuler-20.09-20200929
openEuler-20.03-LTS-20200606
openEuler-20.03-LTS-tag
开始日期   -   截止日期
-
置顶选项
不置顶
置顶等级:高
置顶等级:中
置顶等级:低
优先级
不指定
严重
主要
次要
不重要
预计工期
(小时)
参与者(1)
1
https://gitee.com/src-openeuler/kernel.git
git@gitee.com:src-openeuler/kernel.git
src-openeuler
kernel
kernel
点此查找更多帮助
搜索帮助
Git 命令在线学习
如何在 Gitee 导入 GitHub 仓库
Git 仓库基础操作
企业版和社区版功能对比
SSH 公钥设置
如何处理代码冲突
仓库体积过大,如何减小?
如何找回被删除的仓库数据
Gitee 产品配额说明
GitHub仓库快速导入Gitee及同步更新
什么是 Release(发行版)
将 PHP 项目自动发布到 packagist.org
仓库举报
回到顶部
登录提示
该操作需登录 Gitee 帐号,请先登录后再操作。
立即登录
没有帐号,去注册