CVE-2024-45817 | x86: Deadlock in vlapic_error()

In x86's APIC (Advanced Programmable Interrupt Controller) architecture, error conditions are reported in a status register. Furthermore, the OS can opt to receive an interrupt when a new error occurs. It is possible to configure the error interrupt with an illegal vector, which generates an error when an error interrupt is raised. This case causes Xen to recurse through vlapic_error(). The recursion itself is bounded; errors accumulate in the the status register and only generate an interrupt when a new status bit becomes set. However, the lock protecting this state in Xen will try to be taken recursively, and deadlock.

Published: 2024-09-25 Last update: 2026-01-14 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-45817 is rated Moderate Risk (52.2/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.50%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-45817

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-02-14 0.37% 0.50% +0.13%
2 2026-01-15 0.19% 0.37% +0.18%
3 2025-11-21 — 0.19% —

Full EPSS history (13 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-45817

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.3 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 3.9 3.4 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-45817

OS Trackers for CVE-2024-45817

vendor priority summary link
alpine — CVE-2024-45817: 1 source package rows (xen); 429 state rows across 8 repos (3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, 3.23-main, edge-main); fixed 73, open 356. https://security.alpinelinux.org/vuln/CVE-2024-45817
debian end-of-life CVE-2024-45817 end-of-life priority: Debian including 1 source packages (xen), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2024-45817
suse medium — https://www.suse.com/security/cve/CVE-2024-45817/
ubuntu medium CVE-2024-45817 medium priority: Ubuntu including 1 source packages (xen), 9 status rows across 9 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream, xenial): needs-triage 7, ignored 2. https://ubuntu.com/security/CVE-2024-45817

Affected software / configurations for CVE-2024-45817

Vendor Product Version Raw CPE
xen xen >= 4.5.0 cpe:2.3:o:xen:xen:*:*:*:*:*:*:x86:*

References for CVE-2024-45817

cvelogic Threat Intelligence