# CVE-2024-45817: x86: Deadlock in vlapic_error() > A guest can cause a deadlock in the Xen hypervisor by configuring an illegal APIC error interrupt vector, leading to denial of service. - **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 25 Sep 2024 - **Updated:** 20 Nov 2024 - **Also known as:** ALPINE-CVE-2024-45817, DEBIAN-CVE-2024-45817, GHSA-x9f9-xjf3-f3v6, SUSE-SU-2024:3421-1, SUSE-SU-2024:3422-1, SUSE-SU-2024:3424-1, SUSE-SU-2024:3432-1, UBUNTU-CVE-2024-45817, openSUSE-SU-2024:14377-1 ## What is CVE-2024-45817? CVE-2024-45817 is a high-severity denial of service vulnerability in Xen Xen, published on 25 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information) ## Which versions are affected by CVE-2024-45817? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `xen` | SUSE:Linux Enterprise Micro 5.1 | All versions | 4.14.6_20-150300.3.81.1 | | `xen` | SUSE:Linux Enterprise Micro 5.2 | All versions | 4.14.6_20-150300.3.81.1 | | `xen` | SUSE:Linux Enterprise Micro 5.5 | All versions | 4.17.5_04-150500.3.39.1 | | `xen` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 4.17.5_04-150500.3.39.1 | | `xen` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 4.18.3_04-150600.3.9.1 | | `xen` | SUSE:Linux Enterprise Module for Server Applications 15 SP5 | All versions | 4.17.5_04-150500.3.39.1 | | `xen` | SUSE:Linux Enterprise Module for Server Applications 15 SP6 | All versions | 4.18.3_04-150600.3.9.1 | | `xen` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 4.12.4_54-3.118.1 | | `xen` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 4.12.4_54-3.118.1 | | `xen` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 4.12.4_54-3.118.1 | | `xen` | openSUSE:Leap 15.5 | All versions | 4.17.5_04-150500.3.39.1 | | `xen` | openSUSE:Leap 15.6 | All versions | 4.18.3_04-150600.3.9.1 | | `xen` | openSUSE:Leap Micro 5.5 | All versions | 4.17.5_04-150500.3.39.1 | | `xen` | openSUSE:Tumbleweed | All versions | 4.19.0_04-1.1 | Products: Xen Xen. ## How do I fix CVE-2024-45817? Apply the vendor's patch. ## Is CVE-2024-45817 being exploited? There is no known exploitation of CVE-2024-45817 in the wild and no public exploit code. ## Other vulnerabilities in Xen Xen - [CVE-2017-10912](https://insights.sbomify.com/CVE-2017-10912/): Privilege escalation in n/a (critical 10.0) - [CVE-2017-10918](https://insights.sbomify.com/CVE-2017-10918/): Memory corruption in n/a (critical 10.0) - [CVE-2017-10920](https://insights.sbomify.com/CVE-2017-10920/): Memory corruption in n/a (critical 10.0) - [CVE-2017-10921](https://insights.sbomify.com/CVE-2017-10921/): Memory corruption in n/a (critical 10.0) - [CVE-2025-27466](https://insights.sbomify.com/CVE-2025-27466/): Mutiple vulnerabilities in the Viridian interface (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-45817 and fix it if it is affected. What it is: CVE-2024-45817 is a high-severity denial of service vulnerability in Xen Xen, published on 25 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-45817 in the wild and no public exploit code. Affected product: Xen Xen. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-45817/ (Markdown: https://insights.sbomify.com/CVE-2024-45817/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-45817 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-45817 - OSV: https://osv.dev/vulnerability/CVE-2024-45817 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-45817/ Summaries are generated and may contain mistakes; the official description above is the record.