Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-49927: x86/ioapic: Handle allocation failures gracefully

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 077e1b7cd521163ded545987bbbd389519aeed71, 649a5c2ffae797ce792023a70e84c7fe4b6fb8e0, 830802a0fea8fb39d3dc9fb7d6b5581e1343eb1f; cbl2 kernel 5.15.167.1-2 on CBL Mariner 2.0 5.15.173.1-1; cbl2 kernel 5.15.167.1-2 on CBL-Mariner 2.0 5.15.173.1-1.

Low priority for now. Upgrade to Linux Linux 077e1b7cd521163ded545987bbbd389519aeed71, 649a5c2ffae797ce792023a70e84c7fe4b6fb8e0, 830802a0fea8fb39d3dc9fb7d6b5581e1343eb1f; cbl2 kernel 5.15.167.1-2 on CBL Mariner 2.0 5.15.173.1-1; cbl2 kernel 5.15.167.1-2 on CBL-Mariner 2.0 5.15.173.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Oct 21, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 14th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-49927

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.2affected
    • 49c7e60022912d10da88ba67e8eb2927f1143f6a and later · before e479cb835feeb2abff97f25766e23b96a6eabe28affected · git
    • 49c7e60022912d10da88ba67e8eb2927f1143f6a and later · before ec862cd843faa6f0e84a7a07362f2786446bf697affected · git
    • 49c7e60022912d10da88ba67e8eb2927f1143f6a and later · before 077e1b7cd521163ded545987bbbd389519aeed71affected · git
    • 49c7e60022912d10da88ba67e8eb2927f1143f6a and later · before 649a5c2ffae797ce792023a70e84c7fe4b6fb8e0affected · git
    • 49c7e60022912d10da88ba67e8eb2927f1143f6a and later · before f17efbeb2922327ea01a9efa8829fea9a30e547daffected · git
    • 49c7e60022912d10da88ba67e8eb2927f1143f6a and later · before 830802a0fea8fb39d3dc9fb7d6b5581e1343eb1faffected · git
    • before 4.2not affected · semver
    • 5.15.168 and later · up to and including 5.15.*not affected · semver
    • 6.1.113 and later · up to and including 6.1.*not affected · semver
Affected versions · NVD (5)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernelbefore 5.15.168
  • linux linux kernel5.16 and later · before 6.1.113
  • linux linux kernel6.2 and later · before 6.6.55
  • linux linux kernel6.7 and later · before 6.10.14
  • linux linux kernel6.11 and later · before 6.11.3

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.115-16.1.115-1
Debian:13linuxbefore 6.11.4-16.11.4-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-49924Oct 21, 2024 · fbdev: pxafb: Fix possible use after free in pxafb_task()
    31Monitor
  • ← EarlierCVE-2024-49925Oct 21, 2024 · fbdev: efifb: Register sysfs groups through driver core
    22Monitor
  • Later →CVE-2024-49928Oct 21, 2024 · wifi: rtw89: avoid reading out of bounds when loading TX power FW elements
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux077e1b7cd521163ded545987bbbd389519aeed71Vendor (CNA)
Linux Linux649a5c2ffae797ce792023a70e84c7fe4b6fb8e0Vendor (CNA)
Linux Linux830802a0fea8fb39d3dc9fb7d6b5581e1343eb1fVendor (CNA)
Linux Linuxe479cb835feeb2abff97f25766e23b96a6eabe28Vendor (CNA)
Linux Linuxec862cd843faa6f0e84a7a07362f2786446bf697Vendor (CNA)
Linux Linuxf17efbeb2922327ea01a9efa8829fea9a30e547dVendor (CNA)
cbl2 kernel 5.15.167.1-2 on CBL Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.167.1-2 on CBL-Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.173.1-1 on CBL Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.115-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records