CVE-2024-31145: error handling in x86 IOMMU identity mapping
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.23% (FIRST EPSS).
- Someone with local access to the system can trigger it. Administrator privileges are required. 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.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
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
Certain PCI devices in a system might be assigned Reserved Memory Regions (specified via Reserved Memory Region Reporting, "RMRR") for Intel VT-d or Unity Mapping ranges for AMD-Vi. These are typically used for platform tasks such as legacy USB emulation. Since the precise purpose of these regions is unknown, once a device associated with such a region is active, the mappings of these regions need to remain continuouly accessible by the device. In the logic establishing these mappings, error handling was flawed, resulting in such mappings to potentially remain in place when they should have been removed again. Respective guests would then gain access to memory regions which they aren't supposed to have access to.
- Published
- Sep 25, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- CWE-400
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Running WordPress? Scan your site free with WP Lens
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 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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- xen xen4.0.0 and later
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-460unknown
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.0.0 · before 4.16.6-r1 | 4.16.6-r1 |
| Alpine:v3.18 | xen | from 4.0.0 · before 4.17.5-r0 | 4.17.5-r0 |
| Alpine:v3.19 | xen | from 4.0.0 · before 4.18.3-r0 | 4.18.3-r0 |
| Alpine:v3.21 | xen | from 4.0.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.3_02-150600.3.6.1 | 4.18.3_02-150600.3.6.1 |
| openSUSE:Leap Micro 5.5 | xen | before 4.17.5_02-150500.3.36.1 | 4.17.5_02-150500.3.36.1 |
| openSUSE:Tumbleweed | xen | before 4.19.0_02-1.1 | 4.19.0_02-1.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | xen | before 4.13.5_14-150200.3.96.1 | 4.13.5_14-150200.3.96.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | xen | before 4.14.6_18-150300.3.78.1 | 4.14.6_18-150300.3.78.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.5_02-150500.3.36.1 | 4.17.5_02-150500.3.36.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP6 | xen | before 4.18.3_02-150600.3.6.1 | 4.18.3_02-150600.3.6.1 |
| SUSE:Linux Enterprise Software Development Kit 12 SP5 | xen | before 4.12.4_56-3.121.1 | 4.12.4_56-3.121.1 |
| SUSE:Linux Enterprise Software Development Kit 12 SP5 | xen | before 4.12.4_52-3.115.1 | 4.12.4_52-3.115.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, whi41Plan
- 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 GNTMAP_host41Plan
- 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-2024-31142May 16, 2024 · x86: Incorrect logic for BTC/SRSO mitigations35Monitor
- ← EarlierCVE-2024-31143Jul 18, 2024 · double unlock in x86 guest IRQ handling30Monitor
- Later →CVE-2024-31146Sep 25, 2024 · PCI device pass-through with shared resources30Monitor
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.17.5_02-150500.3.36.1 · openSUSE:Leap Micro 5.5 | Package registry (OSV) |
| suse:xen | 4.13.5_14-150200.3.96.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | Package registry (OSV) |
| suse:xen | 4.17.5_02-150500.3.36.1 · SUSE:Linux Enterprise Micro 5.5 | 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.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Teddy AstieVatesfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-311460 days apartPCI device pass-through with shared resources30Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1548 · Sep 26, 2024(Xen Project Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- Administrator privileges are required.
- 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
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
nvd-secondary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) {
return node.children.map(expand);
}Fixed
const MAX_DEPTH = 32;
function expand(node, depth = 0) {
if (depth > MAX_DEPTH) throw new Error("too deep");
return node.children.map((c) => expand(c, depth + 1));
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- 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.