cveboard RSS feed

CVE-2024-49927

CVE.org · Published

Historical CVEsJSONAI instructions

Record status
Published
Identifier year (not publication year)
2024
Source publication
Source updated
Imported by cveboard
Source snapshot
cve_2026-10-24_midnight_baseline ·

Plain text

CNA source text (English)

x86/ioapic: Handle allocation failures gracefully

In the Linux kernel, the following vulnerability has been resolved: x86/ioapic: Handle allocation failures gracefully Breno observed panics when using failslab under certain conditions during runtime: 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/0x480 That's a pointless panic which is a leftover of the historic IO/APIC code which panic'ed during early boot when the interrupt allocation failed. The only place which might justify panic is the PIT/HPET timer_check() code which tries to figure out whether the timer interrupt is delivered through the IO/APIC. But that code does not require to handle interrupt allocation failures. If the interrupt cannot be allocated then timer delivery fails and 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() and making mp_irqdomain_alloc() aware of the failure condition and handle it as any other failure in this function gracefully.

Scoped product and version facts

Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.

Exploitation unknown; this catalogue does not assess exploitation.

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
unaffected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
49c7e60022912d10da88ba67e8eb2927f1143f6aaffectedgite479cb835feeb2abff97f25766e23b96a6eabe28UnavailableNone listed
49c7e60022912d10da88ba67e8eb2927f1143f6aaffectedgitec862cd843faa6f0e84a7a07362f2786446bf697UnavailableNone listed
49c7e60022912d10da88ba67e8eb2927f1143f6aaffectedgit077e1b7cd521163ded545987bbbd389519aeed71UnavailableNone listed
49c7e60022912d10da88ba67e8eb2927f1143f6aaffectedgit649a5c2ffae797ce792023a70e84c7fe4b6fb8e0UnavailableNone listed
49c7e60022912d10da88ba67e8eb2927f1143f6aaffectedgitf17efbeb2922327ea01a9efa8829fea9a30e547dUnavailableNone listed
49c7e60022912d10da88ba67e8eb2927f1143f6aaffectedgit830802a0fea8fb39d3dc9fb7d6b5581e1343eb1fUnavailableNone listed

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
affected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
4.2affectedUnavailableUnavailableUnavailableNone listed
0unaffectedsemver4.2UnavailableNone listed
5.15.168unaffectedsemverUnavailable5.15.*None listed
6.1.113unaffectedsemverUnavailable6.1.*None listed
6.6.55unaffectedsemverUnavailable6.6.*None listed
6.10.14unaffectedsemverUnavailable6.10.*None listed
6.11.3unaffectedsemverUnavailable6.11.*None listed
6.12unaffectedoriginal_commit_for_fixUnavailable*None listed