# CVE-2025-4598: Race condition in Red Hat Ceph Storage 7 > A local attacker can exploit a race condition in systemd-coredump to read sensitive data from crashed SUID processes, such as /etc/shadow. - **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 30 May 2025 - **Updated:** 15 Oct 2026 - **Also known as:** ALSA-2025:22660, AZL-64289, AZL-64292, AZL-66702, AZL-66704, CLSA-2025-1766079368, DEBIAN-CVE-2025-4598, DLA-4259-1, DSA-5931-1, ECHO-a417-190b-bd77, GHSA-jx2m-wgq5-5qcj, MGASA-2025-0178, OESA-2025-1738, OESA-2025-1739, OESA-2025-1740, OESA-2025-1741, OESA-2025-1764, OESA-2025-1946, RHSA-2025:22660, RHSA-2026:18153, RLSA-2025:22660, RLSA-2026:18153, SUSE-SU-2025:02243-1, SUSE-SU-2025:02244-1, SUSE-SU-2025:02675-1, SUSE-SU-2025:20405-1, SUSE-SU-2025:20416-1, SUSE-SU-2025:20554-1, SUSE-SU-2025:20597-1, UBUNTU-CVE-2025-4598, USN-7559-1, openSUSE-SU-2025:15299-1 ## What is CVE-2025-4598? CVE-2025-4598 is a medium-severity vulnerability in Debian Debian Linux, published on 30 May 2025. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description A vulnerability was found in systemd-coredump. This flaw allows an attacker to force a SUID process to crash and replace it with a non-SUID binary to access the original's privileged process coredump, allowing the attacker to read sensitive data, such as /etc/shadow content, loaded by the original process. A SUID binary or process has a special type of permission, which allows the process to run with the file owner's permissions, regardless of the user executing the binary. This allows the process to access more restricted data than unprivileged users or processes would be able to. An attacker can leverage this flaw by forcing a SUID process to crash and force the Linux kernel to recycle the process PID before systemd-coredump can analyze the /proc/pid/auxv file. If the attacker wins the race condition, they gain access to the original's SUID process coredump file. They can read sensitive content loaded into memory by the original binary, affecting data confidentiality. Weakness: CWE-364 (Signal Handler Race Condition) ## Which versions are affected by CVE-2025-4598? It affects 6 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `rhel-net-naming-sysattrs` | AlmaLinux:9 | All versions | 252-55.el9_7.7.alma.1 | | `systemd` | AlmaLinux:9 | All versions | 252-55.el9_7.7.alma.1 | | `systemd-boot-unsigned` | AlmaLinux:9 | All versions | 252-55.el9_7.7.alma.1 | | `systemd-container` | AlmaLinux:9 | All versions | 252-55.el9_7.7.alma.1 | | `systemd-devel` | AlmaLinux:9 | All versions | 252-55.el9_7.7.alma.1 | | `systemd-journal-remote` | AlmaLinux:9 | All versions | 252-55.el9_7.7.alma.1 | | `systemd-libs` | AlmaLinux:9 | All versions | 252-55.el9_7.7.alma.1 | | `systemd-oomd` | AlmaLinux:9 | All versions | 252-55.el9_7.7.alma.1 | | `systemd-pam` | AlmaLinux:9 | All versions | 252-55.el9_7.7.alma.1 | | `systemd-resolved` | AlmaLinux:9 | All versions | 252-55.el9_7.7.alma.1 | | `systemd-rpm-macros` | AlmaLinux:9 | All versions | 252-55.el9_7.7.alma.1 | | `systemd-udev` | AlmaLinux:9 | All versions | 252-55.el9_7.7.alma.1 | | `systemd-ukify` | AlmaLinux:9 | All versions | 252-55.el9_7.7.alma.1 | | `systemd` | Red Hat:enterprise_linux:10.2 | All versions | 0:257-23.el10 | | `systemd-boot-unsigned` | Red Hat:enterprise_linux:10.2 | All versions | 0:257-23.el10 | | `systemd-container` | Red Hat:enterprise_linux:10.2 | All versions | 0:257-23.el10 | | `systemd-container-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:257-23.el10 | | `systemd-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:257-23.el10 | | `systemd-debugsource` | Red Hat:enterprise_linux:10.2 | All versions | 0:257-23.el10 | | `systemd-devel` | Red Hat:enterprise_linux:10.2 | All versions | 0:257-23.el10 | | `systemd-journal-remote` | Red Hat:enterprise_linux:10.2 | All versions | 0:257-23.el10 | | `systemd-journal-remote-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:257-23.el10 | | `systemd-libs` | Red Hat:enterprise_linux:10.2 | All versions | 0:257-23.el10 | | `systemd-libs-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:257-23.el10 | | `systemd-oomd` | Red Hat:enterprise_linux:10.2 | All versions | 0:257-23.el10 | | `systemd-oomd-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:257-23.el10 | | `systemd-pam` | Red Hat:enterprise_linux:10.2 | All versions | 0:257-23.el10 | | `systemd-pam-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:257-23.el10 | | `systemd-resolved` | Red Hat:enterprise_linux:10.2 | All versions | 0:257-23.el10 | | `systemd-resolved-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:257-23.el10 | | `systemd-rpm-macros` | Red Hat:enterprise_linux:10.2 | All versions | 0:257-23.el10 | | `systemd-tests-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:257-23.el10 | | `systemd-udev` | Red Hat:enterprise_linux:10.2 | All versions | 0:257-23.el10 | | `systemd-udev-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:257-23.el10 | | `systemd-ukify` | Red Hat:enterprise_linux:10.2 | All versions | 0:257-23.el10 | | `systemd-boot-unsigned` | Red Hat:enterprise_linux:9::appstream | All versions | 0:252-55.el9_7.7 | | `systemd-boot-unsigned-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:252-55.el9_7.7 | | `systemd-container-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:252-55.el9_7.7 | | `systemd-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:252-55.el9_7.7 | | `systemd-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:252-55.el9_7.7 | Products: Debian Debian Linux, Linux kernel, Oracle Linux, Redhat Enterprise Linux, Redhat Openshift Container Platform, Systemd Project Systemd. ## How do I fix CVE-2025-4598? Apply the vendor's patch. ## Is CVE-2025-4598 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4598 exists. ## 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-2025-4598 and fix it if it is affected. What it is: CVE-2025-4598 is a medium-severity vulnerability in Debian Debian Linux, published on 30 May 2025. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4598 exists. 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-2025-4598/ (Markdown: https://insights.sbomify.com/CVE-2025-4598/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-4598 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-4598 - OSV: https://osv.dev/vulnerability/CVE-2025-4598 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-4598/ Summaries are generated and may contain mistakes; the official description above is the record.