CVE-2024-49927

一、漏洞信息
 漏洞编号：[CVE-2024-49927](https://nvd.nist.gov/vuln/detail/CVE-2024-49927)
 漏洞归属组件：[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:x86/ioapic: Handle allocation failures gracefullyBreno observed panics when using failslab under certain conditions duringruntime:   can not alloc irq_pin_list (-1,0,20)   Kernel panic - not syncing: IO-APIC: failed to add irq-pin. Can not proceed   panic+0x4e9/0x590   mp_irqdomain_alloc+0x9ab/0xa80   irq_domain_alloc_irqs_locked+0x25d/0x8d0   __irq_domain_alloc_irqs+0x80/0x110   mp_map_pin_to_irq+0x645/0x890   acpi_register_gsi_ioapic+0xe6/0x150   hpet_open+0x313/0x480That s a pointless panic which is a leftover of the historic IO/APIC codewhich panic ed during early boot when the interrupt allocation failed.The only place which might justify panic is the PIT/HPET timer_check() codewhich tries to figure out whether the timer interrupt is delivered throughthe IO/APIC. But that code does not require to handle interrupt allocationfailures. If the interrupt cannot be allocated then timer delivery failsand it either panics due to that or falls back to legacy mode.Cure this by removing the panic wrapper around __add_pin_to_irq_node() andmaking mp_irqdomain_alloc() aware of the failure condition and handle it asany other failure in this function gracefully.
 漏洞公开时间：2024-10-22 02:15:14
 漏洞创建时间：2024-10-22 04:25:26
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2024-49927
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/077e1b7cd521163ded545987bbbd389519aeed71 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/649a5c2ffae797ce792023a70e84c7fe4b6fb8e0 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/830802a0fea8fb39d3dc9fb7d6b5581e1343eb1f |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/e479cb835feeb2abff97f25766e23b96a6eabe28 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/ec862cd843faa6f0e84a7a07362f2786446bf697 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/f17efbeb2922327ea01a9efa8829fea9a30e547d |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-49927 | https://bugzilla.suse.com/show_bug.cgi?id=1232249 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-49927 | https://bugzilla.suse.com/show_bug.cgi?id=1232249 |
| suse_bugzilla | https://git.kernel.org/stable/c/077e1b7cd521163ded545987bbbd389519aeed71 | https://bugzilla.suse.com/show_bug.cgi?id=1232249 |
| suse_bugzilla | https://git.kernel.org/stable/c/649a5c2ffae797ce792023a70e84c7fe4b6fb8e0 | https://bugzilla.suse.com/show_bug.cgi?id=1232249 |
| suse_bugzilla | https://git.kernel.org/stable/c/830802a0fea8fb39d3dc9fb7d6b5581e1343eb1f | https://bugzilla.suse.com/show_bug.cgi?id=1232249 |
| suse_bugzilla | https://git.kernel.org/stable/c/e479cb835feeb2abff97f25766e23b96a6eabe28 | https://bugzilla.suse.com/show_bug.cgi?id=1232249 |
| suse_bugzilla | https://git.kernel.org/stable/c/ec862cd843faa6f0e84a7a07362f2786446bf697 | https://bugzilla.suse.com/show_bug.cgi?id=1232249 |
| suse_bugzilla | https://git.kernel.org/stable/c/f17efbeb2922327ea01a9efa8829fea9a30e547d | https://bugzilla.suse.com/show_bug.cgi?id=1232249 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-49927.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1232249 |
| suse_bugzilla | https://bugzilla.redhat.com/show_bug.cgi?id=2320572 | https://bugzilla.suse.com/show_bug.cgi?id=1232249 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024102125-CVE-2024-49927-86cf@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2320572 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2024-49927 |

</details>

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

无
</details>

二、漏洞分析结构反馈
 影响性分析说明：
  In the Linux kernel, the following vulnerability has been resolved:x86/ioapic: Handle allocation failures gracefullyBreno observed panics when using failslab under certain conditions duringruntime:   can not alloc irq_pin_list (-1,0,20)   Kernel panic - not syncing: IO-APIC: failed to add irq-pin. Can not proceed   panic+0x4e9/0x590   mp_irqdomain_alloc+0x9ab/0xa80   irq_domain_alloc_irqs_locked+0x25d/0x8d0   __irq_domain_alloc_irqs+0x80/0x110   mp_map_pin_to_irq+0x645/0x890   acpi_register_gsi_ioapic+0xe6/0x150   hpet_open+0x313/0x480That s a pointless panic which is a leftover of the historic IO/APIC codewhich panic ed during early boot when the interrupt allocation failed.The only place which might justify panic is the PIT/HPET timer_check() codewhich tries to figure out whether the timer interrupt is delivered throughthe IO/APIC. But that code does not require to handle interrupt allocationfailures. If the interrupt cannot be allocated then timer delivery failsand it either panics due to that or falls back to legacy mode.Cure this by removing the panic wrapper around __add_pin_to_irq_node() andmaking mp_irqdomain_alloc() aware of the failure condition and handle it asany other failure in this function gracefully.
 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-SP1(5.10.0):受影响
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.master(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):否

原因说明：
  1.master(6.6.0):
2.openEuler-20.03-LTS-SP4(4.19.90):
3.openEuler-22.03-LTS-SP1(5.10.0):
4.openEuler-22.03-LTS-SP3(5.10.0):
5.openEuler-22.03-LTS-SP4(5.10.0):
6.openEuler-24.03-LTS(6.6.0):
7.openEuler-24.03-LTS-Next(6.6.0):

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

src-openEuler/kernel
Closed

Content Risk Flag

Comments (8)

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

Content Risk Flag

CVE-2024-49927

Comments (8)

Search

src-openEuler/kernel
Closed