CVE-2023-52879

一、漏洞信息
 漏洞编号：[CVE-2023-52879](https://nvd.nist.gov/vuln/detail/CVE-2023-52879)
 漏洞归属组件：[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：5.5 Medium
  Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
 漏洞简述：
  In the Linux kernel, the following vulnerability has been resolved:tracing: Have trace_event_file have ref countersThe following can crash the kernel: # cd /sys/kernel/tracing # echo  p:sched schedule  > kprobe_events # exec 5>>events/kprobes/sched/enable # > kprobe_events # exec 5>&-The above commands: 1. Change directory to the tracefs directory 2. Create a kprobe event (doesn t matter what one) 3. Open bash file descriptor 5 on the enable file of the kprobe event 4. Delete the kprobe event (removes the files too) 5. Close the bash file descriptor 5The above causes a crash! BUG: kernel NULL pointer dereference, address: 0000000000000028 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 6 PID: 877 Comm: bash Not tainted 6.5.0-rc4-test-00008-g2c6b6b1029d4-dirty #186 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 RIP: 0010:tracing_release_file_tr+0xc/0x50What happens here is that the kprobe event creates a trace_event_file file  descriptor that represents the file in tracefs to the event. Itmaintains state of the event (is it enabled for the given instance?).Opening the  enable  file gets a reference to the event  file  descriptorvia the open file descriptor. When the kprobe event is deleted, the file isalso deleted from the tracefs system which also frees the event  file descriptor.But as the tracefs file is still opened by user space, it will not betotally removed until the final dput() is called on it. But this is nottrue with the event  file  descriptor that is already freed. If the userdoes a write to or simply closes the file descriptor it will reference theevent  file  descriptor that was just freed, causing a use-after-free bug.To solve this, add a ref count to the event  file  descriptor as well as anew flag called  FREED . The  file  will not be freed until the lastreference is released. But the FREE flag will be set when the event isremoved to prevent any more modifications to that event from happening,even if there s still a reference to the event  file  descriptor.
 漏洞公开时间：2024-05-22 00:15:24
 漏洞创建时间：2024-05-22 16:44:11
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2023-52879
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/2c9de867ca285c397cd71af703763fe416265706 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/2fa74d29fc1899c237d51bf9a6e132ea5c488976 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/9034c87d61be8cff989017740a91701ac8195a1d |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/961c4511c7578d6b8f39118be919016ec3db1c1e |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/a98172e36e5f1b3d29ad71fade2d611cfcc2fe6f |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/bb32500fb9b78215e4ef6ee8b4345c5f5d7eafb4 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/cbc7c29dff0fa18162f2a3889d82eeefd67305e0 |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-52879 | https://bugzilla.suse.com/show_bug.cgi?id=1225101 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2023/CVE-2023-52879.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1225101 |
| suse_bugzilla | https://git.kernel.org/stable/c/961c4511c7578d6b8f39118be919016ec3db1c1e | https://bugzilla.suse.com/show_bug.cgi?id=1225101 |
| suse_bugzilla | https://git.kernel.org/stable/c/a98172e36e5f1b3d29ad71fade2d611cfcc2fe6f | https://bugzilla.suse.com/show_bug.cgi?id=1225101 |
| suse_bugzilla | https://git.kernel.org/stable/c/cbc7c29dff0fa18162f2a3889d82eeefd67305e0 | https://bugzilla.suse.com/show_bug.cgi?id=1225101 |
| suse_bugzilla | https://git.kernel.org/stable/c/2fa74d29fc1899c237d51bf9a6e132ea5c488976 | https://bugzilla.suse.com/show_bug.cgi?id=1225101 |
| suse_bugzilla | https://git.kernel.org/stable/c/2c9de867ca285c397cd71af703763fe416265706 | https://bugzilla.suse.com/show_bug.cgi?id=1225101 |
| suse_bugzilla | https://git.kernel.org/stable/c/9034c87d61be8cff989017740a91701ac8195a1d | https://bugzilla.suse.com/show_bug.cgi?id=1225101 |
| suse_bugzilla | https://git.kernel.org/stable/c/bb32500fb9b78215e4ef6ee8b4345c5f5d7eafb4 | https://bugzilla.suse.com/show_bug.cgi?id=1225101 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2023-52879 | https://bugzilla.suse.com/show_bug.cgi?id=1225101 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024052122-CVE-2023-52879-fa4d@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2282730 |
| ubuntu | https://www.cve.org/CVERecord?id=CVE-2023-52879 | https://ubuntu.com/security/CVE-2023-52879 |
| ubuntu | https://git.kernel.org/linus/bb32500fb9b78215e4ef6ee8b4345c5f5d7eafb4 (6.7-rc1) | https://ubuntu.com/security/CVE-2023-52879 |
| ubuntu | https://git.kernel.org/stable/c/961c4511c7578d6b8f39118be919016ec3db1c1e | https://ubuntu.com/security/CVE-2023-52879 |
| ubuntu | https://git.kernel.org/stable/c/a98172e36e5f1b3d29ad71fade2d611cfcc2fe6f | https://ubuntu.com/security/CVE-2023-52879 |
| ubuntu | https://git.kernel.org/stable/c/cbc7c29dff0fa18162f2a3889d82eeefd67305e0 | https://ubuntu.com/security/CVE-2023-52879 |
| ubuntu | https://git.kernel.org/stable/c/2fa74d29fc1899c237d51bf9a6e132ea5c488976 | https://ubuntu.com/security/CVE-2023-52879 |
| ubuntu | https://git.kernel.org/stable/c/2c9de867ca285c397cd71af703763fe416265706 | https://ubuntu.com/security/CVE-2023-52879 |
| ubuntu | https://git.kernel.org/stable/c/9034c87d61be8cff989017740a91701ac8195a1d | https://ubuntu.com/security/CVE-2023-52879 |
| ubuntu | https://git.kernel.org/stable/c/bb32500fb9b78215e4ef6ee8b4345c5f5d7eafb4 | https://ubuntu.com/security/CVE-2023-52879 |
| ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2023-52879 | https://ubuntu.com/security/CVE-2023-52879 |
| ubuntu | https://launchpad.net/bugs/cve/CVE-2023-52879 | https://ubuntu.com/security/CVE-2023-52879 |
| ubuntu | https://security-tracker.debian.org/tracker/CVE-2023-52879 | https://ubuntu.com/security/CVE-2023-52879 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2023-52879 |
| anolis |  | https://anas.openanolis.cn/cves/detail/CVE-2023-52879 |

</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/bb32500fb9b78215e4ef6ee8b4345c5f5d7eafb4 | https://git.kernel.org/linus/f5ca233e2e66dc1c249bf07eefa37e34a6c9346a | ubuntu |
| linux |  | https://git.kernel.org/linus/9034c87d61be8cff989017740a91701ac8195a1d | https://git.kernel.org/linus/f5ca233e2e66dc1c249bf07eefa37e34a6c9346a | ubuntu |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
    In the Linux kernel, the following vulnerability has been resolved:tracing: Have trace_event_file have ref countersThe following can crash the kernel: # cd /sys/kernel/tracing # echo  p:sched schedule  > kprobe_events # exec 5>>events/kprobes/sched/enable # > kprobe_events # exec 5>&-The above commands: 1. Change directory to the tracefs directory 2. Create a kprobe event (doesn t matter what one) 3. Open bash file descriptor 5 on the enable file of the kprobe event 4. Delete the kprobe event (removes the files too) 5. Close the bash file descriptor 5The above causes a crash! BUG: kernel NULL pointer dereference, address: 0000000000000028 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 6 PID: 877 Comm: bash Not tainted 6.5.0-rc4-test-00008-g2c6b6b1029d4-dirty #186 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 RIP: 0010:tracing_release_file_tr+0xc/0x50What happens here is that the kprobe event creates a trace_event_file file  descriptor that represents the file in tracefs to the event. Itmaintains state of the event (is it enabled for the given instance?).Opening the  enable  file gets a reference to the event  file  descriptorvia the open file descriptor. When the kprobe event is deleted, the file isalso deleted from the tracefs system which also frees the event  file descriptor.But as the tracefs file is still opened by user space, it will not betotally removed until the final dput() is called on it. But this is nottrue with the event  file  descriptor that is already freed. If the userdoes a write to or simply closes the file descriptor it will reference theevent  file  descriptor that was just freed, causing a use-after-free bug.To solve this, add a ref count to the event  file  descriptor as well as anew flag called  FREED . The  file  will not be freed until the lastreference is released. But the FREE flag will be set when the event isremoved to prevent any more modifications to that event from happening,even if there s still a reference to the event  file  descriptor. 
 openEuler评分：
  4.4
 Vector：CVSS：3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
 受影响版本排查(受影响/不受影响)：
  1.openEuler-22.03-LTS-SP1(5.10.0):受影响
2.openEuler-22.03-LTS-SP3(5.10.0):受影响
3.openEuler-22.03-LTS-SP4(5.10.0):受影响
4.openEuler-20.03-LTS-SP4(4.19.90):不受影响
5.master(6.6.0):不受影响
6.openEuler-24.03-LTS(6.6.0):不受影响
7.openEuler-24.03-LTS-Next(6.6.0):不受影响
8.openEuler-24.03-LTS-SP2(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):否
8.openEuler-24.03-LTS-SP2(6.6.0):

原因说明：
  1.master(6.6.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.openEuler-24.03-LTS(6.6.0):
6.openEuler-24.03-LTS-Next(6.6.0):
7.openEuler-24.03-LTS-SP1(6.6.0):
8.openEuler-24.03-LTS-SP2(6.6.0):

src-openEuler/kernel
Closed

Content Risk Flag

Comments (52)

src-openEuler/kernelClosed .gitee-modal { width: 500px !important; }

Content Risk Flag

CVE-2023-52879

Comments (52)

Search

src-openEuler/kernel
Closed