pci: phantom functions assigned to incorrect contexts
Noroxi assessment
Priority: Monitor (action score 21/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.80% (FIRST EPSS); higher than 56.2% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: xen (Alpine:v3.16) 4.16.5-r6; xen (Alpine:v3.18) 4.17.3-r0; xen (Alpine:v3.19) 4.18.0-r3.
Low priority for now. Upgrade to xen (Alpine:v3.16) 4.16.5-r6; xen (Alpine:v3.18) 4.17.3-r0; xen (Alpine:v3.19) 4.18.0-r3 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
PCI devices can make use of a functionality called phantom functions, that when enabled allows the device to generate requests using the IDs of functions that are otherwise unpopulated. This allows a device to extend the number of outstanding requests. Such phantom functions need an IOMMU context setup, but failure to setup the context is not fatal when the device is assigned. Not failing device assignment when such failure happens can lead to the primary device being assigned to a guest, while some of the phantom functions are assigned to a different domain.
- Published
- Mar 20, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.8% · 56th percentile
- CWE
- —
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
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 |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- fedoraproject fedora39
- xen xenall versions
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-449unknown
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.16 | xen | before 4.16.5-r6 | 4.16.5-r6 |
| Alpine:v3.18 | xen | before 4.17.3-r0 | 4.17.3-r0 |
| Alpine:v3.19 | xen | before 4.18.0-r3 | 4.18.0-r3 |
| Debian:12 | xen | before 4.17.3+10-g091466ba55-1~deb12u1 | 4.17.3+10-g091466ba55-1~deb12u1 |
| Debian:13 | xen | before 4.17.3+10-g091466ba55-1 | 4.17.3+10-g091466ba55-1 |
| openSUSE:Tumbleweed | xen | before 4.18.0_06-1.1 | 4.18.0_06-1.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | xen | before 4.12.4_44-150100.3.101.1 | 4.12.4_44-150100.3.101.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | xen | before 4.13.5_10-150200.3.86.1 | 4.13.5_10-150200.3.86.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | xen | before 4.14.6_10-150300.3.63.1 | 4.14.6_10-150300.3.63.1 |
| SUSE:Linux Enterprise Micro 5.3 | xen | before 4.16.5_12-150400.4.46.1 | 4.16.5_12-150400.4.46.1 |
| SUSE:Linux Enterprise Micro 5.3 | xen | before 4.16.5_12-150400.4.46.1 | 4.16.5_12-150400.4.46.1 |
| SUSE:Linux Enterprise Micro 5.5 | xen | before 4.17.3_06-150500.3.24.1 | 4.17.3_06-150500.3.24.1 |
| SUSE:Linux Enterprise Micro 5.5 | xen | before 4.17.3_04-150500.3.21.1 | 4.17.3_04-150500.3.21.1 |
| SUSE:Linux Enterprise Micro 5.5 | xen | before 4.17.3_06-150500.3.24.1 | 4.17.3_06-150500.3.24.1 |
| SUSE:Linux Enterprise Micro 5.5 | xen | before 4.17.3_04-150500.3.21.1 | 4.17.3_04-150500.3.21.1 |
| SUSE:Linux Enterprise Software Development Kit 12 SP5 | xen | before 4.12.4_44-3.103.1 | 4.12.4_44-3.103.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-2023-46836Jan 5, 2024 · x86: BTC/SRSO fixes not fully effective18Monitor
- ← EarlierCVE-2023-46837Jan 5, 2024 · arm32: The cache may not be properly cleaned/invalidated (take two)13Monitor
- Later →CVE-2023-46840Mar 20, 2024 · VT-d: Failure to quarantine devices in !HVM builds16Monitor
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.5-r6 · Alpine:v3.16 | Package registry (OSV) |
| debian:xen | 4.17.3+10-g091466ba55-1~deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:xen | 4.17.3_04-150500.3.21.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| suse:xen | 4.14.6_10-150300.3.63.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | Package registry (OSV) |
| suse:xen | 4.17.3_04-150500.3.21.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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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.
- Roger Pau MonnéAMD.finder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
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).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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
- 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.