CVE-2024-35871

一、漏洞信息
 漏洞编号：[CVE-2024-35871](https://nvd.nist.gov/vuln/detail/CVE-2024-35871)
 漏洞归属组件：[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 V2.0分值：
  BaseScore：0.0 None
  Vector：CVSS：2.0/
 漏洞简述：
  In the Linux kernel, the following vulnerability has been resolved:riscv: process: Fix kernel gp leakagechildregs represents the registers which are active for the new threadin user context. For a kernel thread, childregs->gp is never used sincethe kernel gp is not touched by switch_to. For a user mode helper, thegp value can be observed in user space after execve or possibly by othermeans.[From the email thread]The /* Kernel thread */ comment is somewhat inaccurate in that it is also usedfor user_mode_helper threads, which exec a user process, e.g. /sbin/init orwhen /proc/sys/kernel/core_pattern is a pipe. Such threads do not havePF_KTHREAD set and are valid targets for ptrace etc. even before they exec.childregs is the *user* context during syscall execution and it is observablefrom userspace in at least five ways:1. kernel_execve does not currently clear integer registers, so the starting   register state for PID 1 and other user processes started by the kernel has   sp = user stack, gp = kernel __global_pointer$, all other integer registers   zeroed by the memset in the patch comment.   This is a bug in its own right, but I m unwilling to bet that it is the only   way to exploit the issue addressed by this patch.2. ptrace(PTRACE_GETREGSET): you can PTRACE_ATTACH to a user_mode_helper thread   before it execs, but ptrace requires SIGSTOP to be delivered which can only   happen at user/kernel boundaries.3. /proc/*/task/*/syscall: this is perfectly happy to read pt_regs for   user_mode_helpers before the exec completes, but gp is not one of the   registers it returns.4. PERF_SAMPLE_REGS_USER: LOCKDOWN_PERF normally prevents access to kernel   addresses via PERF_SAMPLE_REGS_INTR, but due to this bug kernel addresses   are also exposed via PERF_SAMPLE_REGS_USER which is permitted under   LOCKDOWN_PERF. I have not attempted to write exploit code.5. Much of the tracing infrastructure allows access to user registers. I have   not attempted to determine which forms of tracing allow access to user   registers without already allowing access to kernel registers.
 漏洞公开时间：2024-05-19 17:15:08
 漏洞创建时间：2024-05-23 13:44:04
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2024-35871
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/00effef72c98294edb1efa87ffa0f6cfb61b36a4 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/9abc3e6f1116adb7a2d4fbb8ce20c37916976bf5 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/d14fa1fcf69db9d070e75f1c4425211fa619dfc8 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/d8dcba0691b8e42bddb61aab201e4d918a08e5d9 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/dff6072124f6df77bfd36951fbd88565746980ef |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/f6583444d7e78dae750798552b65a2519ff3ca84 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-35871 | https://bugzilla.suse.com/show_bug.cgi?id=1224528 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-35871 | https://bugzilla.suse.com/show_bug.cgi?id=1224528 |
| suse_bugzilla | https://git.kernel.org/stable/c/00effef72c98294edb1efa87ffa0f6cfb61b36a4 | https://bugzilla.suse.com/show_bug.cgi?id=1224528 |
| suse_bugzilla | https://git.kernel.org/stable/c/9abc3e6f1116adb7a2d4fbb8ce20c37916976bf5 | https://bugzilla.suse.com/show_bug.cgi?id=1224528 |
| suse_bugzilla | https://git.kernel.org/stable/c/d14fa1fcf69db9d070e75f1c4425211fa619dfc8 | https://bugzilla.suse.com/show_bug.cgi?id=1224528 |
| suse_bugzilla | https://git.kernel.org/stable/c/d8dcba0691b8e42bddb61aab201e4d918a08e5d9 | https://bugzilla.suse.com/show_bug.cgi?id=1224528 |
| suse_bugzilla | https://git.kernel.org/stable/c/dff6072124f6df77bfd36951fbd88565746980ef | https://bugzilla.suse.com/show_bug.cgi?id=1224528 |
| suse_bugzilla | https://git.kernel.org/stable/c/f6583444d7e78dae750798552b65a2519ff3ca84 | https://bugzilla.suse.com/show_bug.cgi?id=1224528 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-35871.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1224528 |
| ubuntu | https://www.cve.org/CVERecord?id=CVE-2024-35871 | https://ubuntu.com/security/CVE-2024-35871 |
| ubuntu | https://git.kernel.org/linus/d14fa1fcf69db9d070e75f1c4425211fa619dfc8 (6.9-rc3) | https://ubuntu.com/security/CVE-2024-35871 |
| ubuntu | https://git.kernel.org/stable/c/9abc3e6f1116adb7a2d4fbb8ce20c37916976bf5 | https://ubuntu.com/security/CVE-2024-35871 |
| ubuntu | https://git.kernel.org/stable/c/dff6072124f6df77bfd36951fbd88565746980ef | https://ubuntu.com/security/CVE-2024-35871 |
| ubuntu | https://git.kernel.org/stable/c/f6583444d7e78dae750798552b65a2519ff3ca84 | https://ubuntu.com/security/CVE-2024-35871 |
| ubuntu | https://git.kernel.org/stable/c/00effef72c98294edb1efa87ffa0f6cfb61b36a4 | https://ubuntu.com/security/CVE-2024-35871 |
| ubuntu | https://git.kernel.org/stable/c/d8dcba0691b8e42bddb61aab201e4d918a08e5d9 | https://ubuntu.com/security/CVE-2024-35871 |
| ubuntu | https://git.kernel.org/stable/c/d14fa1fcf69db9d070e75f1c4425211fa619dfc8 | https://ubuntu.com/security/CVE-2024-35871 |
| ubuntu | https://ubuntu.com/security/notices/USN-6893-1 | https://ubuntu.com/security/CVE-2024-35871 |
| ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2024-35871 | https://ubuntu.com/security/CVE-2024-35871 |
| ubuntu | https://launchpad.net/bugs/cve/CVE-2024-35871 | https://ubuntu.com/security/CVE-2024-35871 |
| ubuntu | https://security-tracker.debian.org/tracker/CVE-2024-35871 | https://ubuntu.com/security/CVE-2024-35871 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2024-35871 |
| cve_search |  | https://git.kernel.org/stable/c/9abc3e6f1116adb7a2d4fbb8ce20c37916976bf5 |
| cve_search |  | https://git.kernel.org/stable/c/dff6072124f6df77bfd36951fbd88565746980ef |
| cve_search |  | https://git.kernel.org/stable/c/f6583444d7e78dae750798552b65a2519ff3ca84 |
| cve_search |  | https://git.kernel.org/stable/c/00effef72c98294edb1efa87ffa0f6cfb61b36a4 |
| cve_search |  | https://git.kernel.org/stable/c/d8dcba0691b8e42bddb61aab201e4d918a08e5d9 |
| cve_search |  | https://git.kernel.org/stable/c/d14fa1fcf69db9d070e75f1c4425211fa619dfc8 |

</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/d14fa1fcf69db9d070e75f1c4425211fa619dfc8 | https://git.kernel.org/linus/7db91e57a0acde126a162ababfb1e0ab190130cb | ubuntu |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
                                                            In the Linux kernel, the following vulnerability has been resolved:riscv: process: Fix kernel gp leakagechildregs represents the registers which are active for the new threadin user context. For a kernel thread, childregs->gp is never used sincethe kernel gp is not touched by switch_to. For a user mode helper, thegp value can be observed in user space after execve or possibly by othermeans.[From the email thread]The /* Kernel thread */ comment is somewhat inaccurate in that it is also usedfor user_mode_helper threads, which exec a user process, e.g. /sbin/init orwhen /proc/sys/kernel/core_pattern is a pipe. Such threads do not havePF_KTHREAD set and are valid targets for ptrace etc. even before they exec.childregs is the *user* context during syscall execution and it is observablefrom userspace in at least five ways:1. kernel_execve does not currently clear integer registers, so the starting   register state for PID 1 and other user processes started by the kernel has   sp = user stack, gp = kernel __global_pointer$, all other integer registers   zeroed by the memset in the patch comment.   This is a bug in its own right, but I m unwilling to bet that it is the only   way to exploit the issue addressed by this patch.2. ptrace(PTRACE_GETREGSET): you can PTRACE_ATTACH to a user_mode_helper thread   before it execs, but ptrace requires SIGSTOP to be delivered which can only   happen at user/kernel boundaries.3. /proc/*/task/*/syscall: this is perfectly happy to read pt_regs for   user_mode_helpers before the exec completes, but gp is not one of the   registers it returns.4. PERF_SAMPLE_REGS_USER: LOCKDOWN_PERF normally prevents access to kernel   addresses via PERF_SAMPLE_REGS_INTR, but due to this bug kernel addresses   are also exposed via PERF_SAMPLE_REGS_USER which is permitted under   LOCKDOWN_PERF. I have not attempted to write exploit code.5. Much of the tracing infrastructure allows access to user registers. I have   not attempted to determine which forms of tracing allow access to user   registers without already allowing access to kernel registers.                             
 openEuler评分：
  5.5
 Vector：CVSS：2.0/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N
 受影响版本排查(受影响/不受影响)：
  1.openEuler-22.03-LTS-SP1(5.10.0):受影响
2.openEuler-22.03-LTS-SP3(5.10.0):受影响
3.openEuler-20.03-LTS-SP1(4.19.90):不受影响
4.openEuler-20.03-LTS-SP4(4.19.90):不受影响
5.openEuler-22.03-LTS(5.10.0):不受影响
6.openEuler-22.03-LTS-SP2(5.10.0):不受影响
7.openEuler-22.03-LTS-SP4(5.10.0):不受影响
8.master(6.6.0):不受影响
9.openEuler-22.03-LTS-Next(5.10.0):不受影响
10.openEuler-24.03-LTS(6.6.0):不受影响
11.openEuler-24.03-LTS-Next(6.6.0):不受影响

修复是否涉及abi变化(是/否)：
  1.openEuler-20.03-LTS-SP1(4.19.90):否
2.openEuler-20.03-LTS-SP4(4.19.90):否
3.openEuler-22.03-LTS(5.10.0):否
4.openEuler-22.03-LTS-SP1(5.10.0):否
5.openEuler-22.03-LTS-SP2(5.10.0):否
6.openEuler-22.03-LTS-SP3(5.10.0):否
7.master(6.6.0):否
8.openEuler-22.03-LTS-Next(5.10.0):否
9.openEuler-24.03-LTS(6.6.0):否
10.openEuler-24.03-LTS-Next(6.6.0):否
11.openEuler-22.03-LTS-SP4(5.10.0):否

三、漏洞修复
安全公告链接：https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2024-2295

src-openEuler/kernel
关闭

内容风险标识

评论 (53)

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

内容风险标识

CVE-2024-35871

评论 (53)

搜索帮助

src-openEuler/kernel
关闭