# CVE-2023-46839: pci: phantom functions assigned to incorrect contexts > Attackers can exploit phantom function misconfiguration to access resources in a different domain, leading to privilege escalation or data leakage. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 20 Mar 2024 - **Updated:** 4 Nov 2025 - **Also known as:** ALPINE-CVE-2023-46839, DEBIAN-CVE-2023-46839, GHSA-8f65-fxmq-vvpx, SUSE-SU-2024:0264-1, SUSE-SU-2024:0265-1, SUSE-SU-2024:0268-1, SUSE-SU-2024:0269-1, SUSE-SU-2024:0270-1, UBUNTU-CVE-2023-46839 ## What is CVE-2023-46839? CVE-2023-46839 is a medium-severity missing authorization vulnerability in Fedoraproject Fedora, published on 20 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. ## Which versions are affected by CVE-2023-46839? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `xen` | SUSE:Enterprise Storage 7.1 | All versions | 4.14.6_10-150300.3.63.1 | | `xen` | SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | All versions | 4.12.4_44-150100.3.101.1 | | `xen` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 4.13.5_10-150200.3.86.1 | | `xen` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 4.14.6_10-150300.3.63.1 | | `xen` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 4.16.5_12-150400.4.46.1 | | `xen` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 4.16.5_12-150400.4.46.1 | | `xen` | SUSE:Linux Enterprise Micro 5.1 | All versions | 4.14.6_10-150300.3.63.1 | | `xen` | SUSE:Linux Enterprise Micro 5.2 | All versions | 4.14.6_10-150300.3.63.1 | | `xen` | SUSE:Linux Enterprise Micro 5.3 | All versions | 4.16.5_12-150400.4.46.1 | | `xen` | SUSE:Linux Enterprise Micro 5.4 | All versions | 4.16.5_12-150400.4.46.1 | | `xen` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 4.12.4_44-3.103.1 | | `xen` | SUSE:Linux Enterprise Server 15 SP1-LTSS | All versions | 4.12.4_44-150100.3.101.1 | | `xen` | SUSE:Linux Enterprise Server 15 SP2-LTSS | All versions | 4.13.5_10-150200.3.86.1 | | `xen` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 4.14.6_10-150300.3.63.1 | | `xen` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 4.16.5_12-150400.4.46.1 | | `xen` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 4.12.4_44-3.103.1 | | `xen` | SUSE:Linux Enterprise Server for SAP Applications 15 SP1 | All versions | 4.12.4_44-150100.3.101.1 | | `xen` | SUSE:Linux Enterprise Server for SAP Applications 15 SP2 | All versions | 4.13.5_10-150200.3.86.1 | | `xen` | SUSE:Linux Enterprise Server for SAP Applications 15 SP3 | All versions | 4.14.6_10-150300.3.63.1 | | `xen` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 4.16.5_12-150400.4.46.1 | | `xen` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 4.12.4_44-3.103.1 | | `xen` | SUSE:Manager Proxy 4.3 | All versions | 4.16.5_12-150400.4.46.1 | | `xen` | SUSE:Manager Server 4.3 | All versions | 4.16.5_12-150400.4.46.1 | | `xen` | openSUSE:Leap Micro 5.3 | All versions | 4.16.5_12-150400.4.46.1 | | `xen` | openSUSE:Leap Micro 5.4 | All versions | 4.16.5_12-150400.4.46.1 | Products: Fedoraproject Fedora, Xen Xen. ## How do I fix CVE-2023-46839? Apply the vendor's patch. ## Is CVE-2023-46839 being exploited? There is no known exploitation of CVE-2023-46839 in the wild and no public exploit code. ## Other vulnerabilities in Fedoraproject Fedora - [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild) - [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild) - [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-46839 and fix it if it is affected. What it is: CVE-2023-46839 is a medium-severity missing authorization vulnerability in Fedoraproject Fedora, published on 20 Mar 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-2023-46839 in the wild and no public exploit code. Affected product: Fedoraproject Fedora. 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-2023-46839/ (Markdown: https://insights.sbomify.com/CVE-2023-46839/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-46839 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-46839 - OSV: https://osv.dev/vulnerability/CVE-2023-46839 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-46839/ Summaries are generated and may contain mistakes; the official description above is the record.