# CVE-2023-41915: Race condition in n/a > Attackers can gain ownership of arbitrary files via a race condition in PMIx library code running with root privileges. - **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 9 Sep 2023 - **Updated:** 2 Aug 2024 - **Also known as:** ALSA-2024:2199, ALSA-2024:3008, AZL-29702, CLSA-2025-1763123299, DEBIAN-CVE-2023-41915, DLA-3643-1, DSA-5547-1, GHSA-m8fg-c37h-w29q, MGASA-2024-0162, OESA-2023-1676, RHSA-2024:2199, RHSA-2024:3008, RLSA-2024:2199, RLSA-2024:3008, SUSE-SU-2023:3859-1, UBUNTU-CVE-2023-41915, USN-6434-1, openSUSE-SU-2024:13223-1 ## What is CVE-2023-41915? CVE-2023-41915 is a high-severity vulnerability in Debian Debian Linux, published on 9 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description OpenPMIx PMIx before 4.2.6 and 5.0.x before 5.0.1 allows attackers to obtain ownership of arbitrary files via a race condition during execution of library code with UID 0. Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization) ## Which versions are affected by CVE-2023-41915? It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `pmix` | AlmaLinux:8 | All versions | 2.2.5-3.el8 | | `pmix-devel` | AlmaLinux:8 | All versions | 2.2.5-3.el8 | | `pmix` | AlmaLinux:9 | All versions | 3.2.3-5.el9 | | `pmix-devel` | AlmaLinux:9 | All versions | 3.2.3-5.el9 | | `pmix-pmi` | AlmaLinux:9 | All versions | 3.2.3-5.el9 | | `pmix-pmi-devel` | AlmaLinux:9 | All versions | 3.2.3-5.el9 | | `pmix-tools` | AlmaLinux:9 | All versions | 3.2.3-5.el9 | | `pmix` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.2.5-3.el8 | | `pmix-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.2.5-3.el8 | | `pmix-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.2.5-3.el8 | | `pmix-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.2.5-3.el8 | | `pmix-debugsource` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.2.5-3.el8 | | `pmix-devel` | Red Hat:enterprise_linux:8::crb | All versions | 0:2.2.5-3.el8 | | `pmix` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.2.3-5.el9 | | `pmix-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.2.3-5.el9 | | `pmix-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.2.3-5.el9 | | `pmix-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.2.3-5.el9 | | `pmix-pmi` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.2.3-5.el9 | | `pmix-pmi-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.2.3-5.el9 | | `pmix-tools` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.2.3-5.el9 | | `pmix-tools-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.2.3-5.el9 | | `pmix-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:3.2.3-5.el9 | | `pmix-debugsource` | Red Hat:enterprise_linux:9::crb | All versions | 0:3.2.3-5.el9 | | `pmix-pmi-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:3.2.3-5.el9 | | `pmix-pmi-devel` | Red Hat:enterprise_linux:9::crb | All versions | 0:3.2.3-5.el9 | | `pmix-tools-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:3.2.3-5.el9 | | `pmix` | Rocky Linux:8 | All versions | 0:2.2.5-3.el8 | | `pmix` | Rocky Linux:9 | All versions | 0:3.2.3-5.el9 | | `pmix` | SUSE:Linux Enterprise Module for HPC 15 SP4 | All versions | 3.2.3-150300.3.8.1 | | `pmix` | SUSE:Linux Enterprise Module for HPC 15 SP5 | All versions | 3.2.3-150300.3.8.1 | | `pmix` | openSUSE:Leap 15.4 | All versions | 3.2.3-150300.3.8.1 | | `pmix` | openSUSE:Leap 15.5 | All versions | 3.2.3-150300.3.8.1 | Products: Debian Debian Linux, Fedoraproject Fedora, Openpmix Openpmix. ## How do I fix CVE-2023-41915? Upgrade to a fixed version. ## Is CVE-2023-41915 being exploited? There is no known exploitation of CVE-2023-41915 in the wild and no public exploit code. ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-41915 and fix it if it is affected. What it is: CVE-2023-41915 is a high-severity vulnerability in Debian Debian Linux, published on 9 Sep 2023. 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-41915 in the wild and no public exploit code. Affected product: Debian Debian Linux. 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-41915/ (Markdown: https://insights.sbomify.com/CVE-2023-41915/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-41915 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-41915 - OSV: https://osv.dev/vulnerability/CVE-2023-41915 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-41915/ Summaries are generated and may contain mistakes; the official description above is the record.