CVE-2024-31143: double unlock in x86 guest IRQ handling
Noroxi assessment
Priority: Monitor (action score 30/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.50% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: xen (Alpine:v3.17) 4.16.6-r1; xen (Alpine:v3.18) 4.17.5-r0; xen (Alpine:v3.19) 4.18.3-r0.
Low priority for now. Upgrade to xen (Alpine:v3.17) 4.16.6-r1; xen (Alpine:v3.18) 4.17.5-r0; xen (Alpine:v3.19) 4.18.3-r0 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
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.
- Published
- Jul 18, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.5% · 43th percentile
- CWE
- CWE-832
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| xen | xen | cpe:2.3:o:xen:xen |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (XEN). Independent of NVD's CPE analysis and usually ahead of it.
Xen Xen
- consult Xen advisory XSA-458unknown
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- xen xen4.4.0 and later
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.17 | xen | from 4.4.0 · before 4.16.6-r1 | 4.16.6-r1 |
| Alpine:v3.18 | xen | from 4.4.0 · before 4.17.5-r0 | 4.17.5-r0 |
| Alpine:v3.19 | xen | from 4.4.0 · before 4.18.3-r0 | 4.18.3-r0 |
| Alpine:v3.21 | xen | from 4.4.0 · before 4.19.0-r0 | 4.19.0-r0 |
| Debian:12 | xen | before 4.17.5+23-ga4e5191dc0-1 | 4.17.5+23-ga4e5191dc0-1 |
| Debian:13 | xen | before 4.19.1-1 | 4.19.1-1 |
| openSUSE:Leap 15.6 | xen | before 4.18.2_06-150600.3.3.1 | 4.18.2_06-150600.3.3.1 |
| openSUSE:Leap Micro 5.5 | xen | before 4.17.4_04-150500.3.33.1 | 4.17.4_04-150500.3.33.1 |
| openSUSE:Tumbleweed | xen | before 4.18.2_06-2.1 | 4.18.2_06-2.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | xen | before 4.13.5_12-150200.3.93.1 | 4.13.5_12-150200.3.93.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | xen | before 4.14.6_16-150300.3.75.1 | 4.14.6_16-150300.3.75.1 |
| SUSE:Linux Enterprise Micro 5.3 | xen | before 4.16.6_04-150400.4.62.1 | 4.16.6_04-150400.4.62.1 |
| SUSE:Linux Enterprise Micro 5.5 | xen | before 4.17.4_04-150500.3.33.1 | 4.17.4_04-150500.3.33.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP6 | xen | before 4.18.2_06-150600.3.3.1 | 4.18.2_06-150600.3.3.1 |
| SUSE:Linux Enterprise Software Development Kit 12 SP5 | xen | before 4.12.4_50-3.112.1 | 4.12.4_50-3.112.1 |
Same product
xen: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-10921The grant-table feature in Xen through 4.8.x does not ensure sufficient type counts for a GNTMAP_device_map and GNTMAP_host_map mapping…41Plan
- CVE-2017-10920The grant-table feature in Xen through 4.8.x mishandles a GNTMAP_device_map and GNTMAP_host_map mapping, when followed by only a…41Plan
- CVE-2017-10918Xen through 4.8.x does not validate memory allocations during certain P2M operations, which allows guest OS users to obtain privileged host…41Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-46842May 16, 2024 · x86 HVM hypercalls may trigger Xen bug check29Monitor
- ← EarlierCVE-2024-31142May 16, 2024 · x86: Incorrect logic for BTC/SRSO mitigations35Monitor
- Later →CVE-2024-31145Sep 25, 2024 · error handling in x86 IOMMU identity mapping30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:xen | 4.16.6-r1 · Alpine:v3.17 | Package registry (OSV) |
| debian:xen | 4.17.5+23-ga4e5191dc0-1 · Debian:12 | Package registry (OSV) |
| opensuse:xen | 4.18.2_06-150600.3.3.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:xen | 4.18.2_06-150600.3.3.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6 | Package 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.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Jan BeulichSUSE.finder
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-832 · Unlock of a Resource that is not LockedCVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.