# CVE-2024-31143: double unlock in x86 guest IRQ handling

> A double unlock error in Xen's PCI MSI handling can cause a denial of service in x86 guest IRQ processing.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Jul 2024
- **Updated:** 26 Apr 2025
- **Also known as:** ALPINE-CVE-2024-31143, DEBIAN-CVE-2024-31143, GHSA-cjq8-723f-8fmv, UBUNTU-CVE-2024-31143, openSUSE-SU-2024:14204-1

## What is CVE-2024-31143?

CVE-2024-31143 is a high-severity vulnerability in Xen Xen, published on 18 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An optional feature of PCI MSI called "Multiple Message" allows a
device to use multiple consecutive interrupt vectors.  Unlike for MSI-X,
the setting up of these consecutive vectors needs to happen all in one
go.  In this handling an error path could be taken in different
situations, with or without a particular lock held.  This error path
wrongly releases the lock even when it is not currently held.

Weakness: CWE-832 (Unlock of a Resource that is not Locked)

## Which versions are affected by CVE-2024-31143?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `xen` | openSUSE:Tumbleweed | All versions | 4.18.2_06-2.1 |

Products: Xen Xen.

## How do I fix CVE-2024-31143?

Apply the vendor's patch.

## Is CVE-2024-31143 being exploited?

There is no known exploitation of CVE-2024-31143 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-31143 and fix it if it is affected.

What it is: CVE-2024-31143 is a high-severity vulnerability in Xen Xen, published on 18 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-31143 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-31143/ (Markdown: https://insights.sbomify.com/CVE-2024-31143/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-31143
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-31143
- OSV: https://osv.dev/vulnerability/CVE-2024-31143

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-31143/
Summaries are generated and may contain mistakes; the official description above is the record.