CVE-2024-53195

一、漏洞信息
 漏洞编号：[CVE-2024-53195](https://nvd.nist.gov/vuln/detail/CVE-2024-53195)
 漏洞归属组件：[kernel](https://gitee.com/src-openeuler/kernel)
 漏洞归属的版本：4.19.140,4.19.194,4.19.90,5.10.0,6.1.19,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:KVM: arm64: Get rid of userspace_irqchip_in_useImproper use of userspace_irqchip_in_use led to syzbot hitting thefollowing WARN_ON() in kvm_timer_update_irq():WARNING: CPU: 0 PID: 3281 at arch/arm64/kvm/arch_timer.c:459kvm_timer_update_irq+0x21c/0x394Call trace:  kvm_timer_update_irq+0x21c/0x394 arch/arm64/kvm/arch_timer.c:459  kvm_timer_vcpu_reset+0x158/0x684 arch/arm64/kvm/arch_timer.c:968  kvm_reset_vcpu+0x3b4/0x560 arch/arm64/kvm/reset.c:264  kvm_vcpu_set_target arch/arm64/kvm/arm.c:1553 [inline]  kvm_arch_vcpu_ioctl_vcpu_init arch/arm64/kvm/arm.c:1573 [inline]  kvm_arch_vcpu_ioctl+0x112c/0x1b3c arch/arm64/kvm/arm.c:1695  kvm_vcpu_ioctl+0x4ec/0xf74 virt/kvm/kvm_main.c:4658  vfs_ioctl fs/ioctl.c:51 [inline]  __do_sys_ioctl fs/ioctl.c:907 [inline]  __se_sys_ioctl fs/ioctl.c:893 [inline]  __arm64_sys_ioctl+0x108/0x184 fs/ioctl.c:893  __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]  invoke_syscall+0x78/0x1b8 arch/arm64/kernel/syscall.c:49  el0_svc_common+0xe8/0x1b0 arch/arm64/kernel/syscall.c:132  do_el0_svc+0x40/0x50 arch/arm64/kernel/syscall.c:151  el0_svc+0x54/0x14c arch/arm64/kernel/entry-common.c:712  el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730  el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598The following sequence led to the scenario: - Userspace creates a VM and a vCPU. - The vCPU is initialized with KVM_ARM_VCPU_PMU_V3 during   KVM_ARM_VCPU_INIT. - Without any other setup, such as vGIC or vPMU, userspace issues   KVM_RUN on the vCPU. Since the vPMU is requested, but not setup,   kvm_arm_pmu_v3_enable() fails in kvm_arch_vcpu_run_pid_change().   As a result, KVM_RUN returns after enabling the timer, but before   incrementing  userspace_irqchip_in_use :   kvm_arch_vcpu_run_pid_change()       ret = kvm_arm_pmu_v3_enable()           if (!vcpu->arch.pmu.created)               return -EINVAL;       if (ret)           return ret;       [...]       if (!irqchip_in_kernel(kvm))           static_branch_inc(&userspace_irqchip_in_use); - Userspace ignores the error and issues KVM_ARM_VCPU_INIT again.   Since the timer is already enabled, control moves through the   following flow, ultimately hitting the WARN_ON():   kvm_timer_vcpu_reset()       if (timer->enabled)          kvm_timer_update_irq()              if (!userspace_irqchip())                  ret = kvm_vgic_inject_irq()                      ret = vgic_lazy_init()                          if (unlikely(!vgic_initialized(kvm)))                              if (kvm->arch.vgic.vgic_model !=                                  KVM_DEV_TYPE_ARM_VGIC_V2)                                      return -EBUSY;                  WARN_ON(ret);Theoretically, since userspace_irqchip_in_use s functionality can besimply replaced by  !irqchip_in_kernel() , get rid of the static keyto avoid the mismanagement, which also helps with the syzbot issue.
 漏洞公开时间：2024-12-27 22:15:27
 漏洞创建时间：2024-12-27 22:43:12
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2024-53195
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/38d7aacca09230fdb98a34194fec2af597e8e20d |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/c16e2dba39ff6ae84bb8dc9c8e0fb21d9b2f6f5c |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/dd2f9861f27571d47998d71e7516bf7216db0b52 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/fe425d5239a28c21e0c83ee7a8f4cb210d29fdb4 |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-53195 | https://bugzilla.suse.com/show_bug.cgi?id=1234957 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-53195 | https://bugzilla.suse.com/show_bug.cgi?id=1234957 |
| suse_bugzilla | https://git.kernel.org/stable/c/38d7aacca09230fdb98a34194fec2af597e8e20d | https://bugzilla.suse.com/show_bug.cgi?id=1234957 |
| suse_bugzilla | https://git.kernel.org/stable/c/c16e2dba39ff6ae84bb8dc9c8e0fb21d9b2f6f5c | https://bugzilla.suse.com/show_bug.cgi?id=1234957 |
| suse_bugzilla | https://git.kernel.org/stable/c/dd2f9861f27571d47998d71e7516bf7216db0b52 | https://bugzilla.suse.com/show_bug.cgi?id=1234957 |
| suse_bugzilla | https://git.kernel.org/stable/c/fe425d5239a28c21e0c83ee7a8f4cb210d29fdb4 | https://bugzilla.suse.com/show_bug.cgi?id=1234957 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-53195.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1234957 |
| suse_bugzilla | https://bugzilla.redhat.com/show_bug.cgi?id=2334383 | https://bugzilla.suse.com/show_bug.cgi?id=1234957 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2024-53195 |
| anolis |  | https://anas.openanolis.cn/cves/detail/CVE-2024-53195 |

</details>

漏洞分析指导链接：
  https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
 漏洞数据来源:
  openBrain开源漏洞感知系统
 漏洞补丁信息：
  <details>
<summary>详情(点击展开)</summary>

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
| linux_kernel | 6.6.64 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=dd2f9861f27571d47998d71e7516bf7216db0b52 |  | linuxkernelcves |
| linux_kernel | 6.11.11 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c16e2dba39ff6ae84bb8dc9c8e0fb21d9b2f6f5c |  | linuxkernelcves |
| linux_kernel | 6.12.2 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=fe425d5239a28c21e0c83ee7a8f4cb210d29fdb4 |  | linuxkernelcves |
| linux_kernel | 6.13-rc1 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=38d7aacca09230fdb98a34194fec2af597e8e20d |  | linuxkernelcves |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
  Reserved.
 openEuler评分：
  5.5
 Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
 受影响版本排查(受影响/不受影响)：
  1.openEuler-20.03-LTS-SP4(4.19.90):受影响
2.openEuler-22.03-LTS-SP3(5.10.0):受影响
3.openEuler-22.03-LTS-SP4(5.10.0):受影响
4.openEuler-24.03-LTS(6.6.0):受影响
5.openEuler-24.03-LTS-SP1(6.6.0):受影响
6.master(6.12.33):不受影响
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.12.33):否
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-SP1(6.6.0):否

原因说明：
  1.openEuler-24.03-LTS(6.6.0):正常修复
2.openEuler-24.03-LTS-SP1(6.6.0):正常修复
3.openEuler-22.03-LTS-SP3(5.10.0):暂不修复-漏洞仍在分析中
4.openEuler-22.03-LTS-SP4(5.10.0):暂不修复-漏洞仍在分析中
5.openEuler-20.03-LTS-SP4(4.19.90):不修复-超出修复范围
6.master(6.12.33):不受影响-漏洞代码不能被攻击者触发
7.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不能被攻击者触发

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

src-openEuler/kernel

Content Risk Flag

Comments (7)

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

Content Risk Flag

CVE-2024-53195

Comments (7)

Search

src-openEuler/kernel