Release Date: | 2024-10-21 |
In the Linux kernel, the following vulnerability has been resolved:\nx86/ioapic: Handle allocation failures gracefully\nBreno observed panics when using failslab under certain conditions during\nruntime:\ncan not alloc irq_pin_list (-1,0,20)\nKernel panic - not syncing: IO-APIC: failed to add irq-pin. Can not proceed\npanic+0x4e9/0x590\nmp_irqdomain_alloc+0x9ab/0xa80\nirq_domain_alloc_irqs_locked+0x25d/0x8d0\n__irq_domain_alloc_irqs+0x80/0x110\nmp_map_pin_to_irq+0x645/0x890\nacpi_register_gsi_ioapic+0xe6/0x150\nhpet_open+0x313/0x480\nThat's a pointless panic which is a leftover of the historic IO/APIC code\nwhich panic'ed during early boot when the interrupt allocation failed.\nThe only place which might justify panic is the PIT/HPET timer_check() code\nwhich tries to figure out whether the timer interrupt is delivered through\nthe IO/APIC. But that code does not require to handle interrupt allocation\nfailures. If the interrupt cannot be allocated then timer delivery fails\nand it either panics due to that or falls back to legacy mode.\nCure this by removing the panic wrapper around __add_pin_to_irq_node() and\nmaking mp_irqdomain_alloc() aware of the failure condition and handle it as\nany other failure in this function gracefully.
See more information about CVE-2024-49927 from MITRE CVE dictionary and NIST NVD
NOTE: The following CVSS metrics and score provided are preliminary and subject to review.
Base Score: | 5.5 |
Vector String: | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Version: | 3.1 |
Attack Vector: | Local |
Attack Complexity: | Low |
Privileges Required: | Low |
User Interaction: | None |
Scope: | Unchanged |
Confidentiality: | None |
Integrity: | None |
Availability: | High |
Platform | Errata | Release Date |
Oracle Linux version 8 (kernel-uek) | ELSA-2024-12887 | 2024-12-18 |
Oracle Linux version 9 (kernel-uek) | ELSA-2024-12887 | 2024-12-18 |
This page is generated automatically and has not been checked for errors or omissions. For clarification or corrections: