CVE-2025-30472 Memory corruption in Corosync
Critical 9.0
Published
Updated
Check this codebase for CVE-2025-30472 and fix it if it is affected.
What it is: CVE-2025-30472 is a critical memory corruption vulnerability in Corosync, published on 22 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-30472 exists.
Affected product: Corosync. 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-30472/ (Markdown: https://insights.sbomify.com/CVE-2025-30472/index.md)
A stack-based buffer overflow in Corosync allows remote code execution or denial of service if encryption is disabled or the key is known.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-30472?
CVE-2025-30472 is a critical memory corruption vulnerability in Corosync, published on 22 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Corosync through 3.1.9, if encryption is disabled or the attacker knows the encryption key, has a stack-based buffer overflow in orf_token_endian_convert in exec/totemsrp.c via a large UDP packet.
Which versions are affected by CVE-2025-30472?
It affects 1 product.
Linux distribution packages (40)
corosync-vqsim AlmaLinux:10 | All versions | 3.1.9-1.el10_0.1 |
corosynclib AlmaLinux:10 | All versions | 3.1.9-1.el10_0.1 |
corosync-vqsim AlmaLinux:9 | All versions | 3.1.9-2.el9_6 |
corosynclib AlmaLinux:9 | All versions | 3.1.9-2.el9_6 |
corosync Red Hat:enterprise_linux:10.0 | All versions | 0:3.1.9-1.el10_0.1 |
corosync-debuginfo Red Hat:enterprise_linux:10.0 | All versions | 0:3.1.9-1.el10_0.1 |
corosync-debugsource Red Hat:enterprise_linux:10.0 | All versions | 0:3.1.9-1.el10_0.1 |
corosync-vqsim Red Hat:enterprise_linux:10.0 | All versions | 0:3.1.9-1.el10_0.1 |
corosync-vqsim-debuginfo Red Hat:enterprise_linux:10.0 | All versions | 0:3.1.9-1.el10_0.1 |
corosynclib Red Hat:enterprise_linux:10.0 | All versions | 0:3.1.9-1.el10_0.1 |
corosynclib-debuginfo Red Hat:enterprise_linux:10.0 | All versions | 0:3.1.9-1.el10_0.1 |
corosynclib-devel Red Hat:enterprise_linux:10.0 | All versions | 0:3.1.9-1.el10_0.1 |
corosync Red Hat:enterprise_linux:9::appstream | All versions | 0:3.1.9-2.el9_6 |
corosync-debuginfo Red Hat:enterprise_linux:9::appstream | All versions | 0:3.1.9-2.el9_6 |
corosync-debugsource Red Hat:enterprise_linux:9::appstream | All versions | 0:3.1.9-2.el9_6 |
corosync-vqsim-debuginfo Red Hat:enterprise_linux:9::appstream | All versions | 0:3.1.9-2.el9_6 |
corosynclib Red Hat:enterprise_linux:9::appstream | All versions | 0:3.1.9-2.el9_6 |
corosynclib-debuginfo Red Hat:enterprise_linux:9::appstream | All versions | 0:3.1.9-2.el9_6 |
corosync-debuginfo Red Hat:enterprise_linux:9::crb | All versions | 0:3.1.9-2.el9_6 |
corosync-debugsource Red Hat:enterprise_linux:9::crb | All versions | 0:3.1.9-2.el9_6 |
corosync-vqsim Red Hat:enterprise_linux:9::crb | All versions | 0:3.1.9-2.el9_6 |
corosync-vqsim-debuginfo Red Hat:enterprise_linux:9::crb | All versions | 0:3.1.9-2.el9_6 |
corosynclib-debuginfo Red Hat:enterprise_linux:9::crb | All versions | 0:3.1.9-2.el9_6 |
corosync Red Hat:enterprise_linux:9::highavailability | All versions | 0:3.1.9-2.el9_6 |
corosync-debuginfo Red Hat:enterprise_linux:9::highavailability | All versions | 0:3.1.9-2.el9_6 |
corosync-debugsource Red Hat:enterprise_linux:9::highavailability | All versions | 0:3.1.9-2.el9_6 |
corosync-vqsim-debuginfo Red Hat:enterprise_linux:9::highavailability | All versions | 0:3.1.9-2.el9_6 |
corosynclib-debuginfo Red Hat:enterprise_linux:9::highavailability | All versions | 0:3.1.9-2.el9_6 |
corosynclib-devel Red Hat:enterprise_linux:9::highavailability | All versions | 0:3.1.9-2.el9_6 |
corosync Red Hat:enterprise_linux:9::resilientstorage | All versions | 0:3.1.9-2.el9_6 |
corosync-debuginfo Red Hat:enterprise_linux:9::resilientstorage | All versions | 0:3.1.9-2.el9_6 |
corosync-debugsource Red Hat:enterprise_linux:9::resilientstorage | All versions | 0:3.1.9-2.el9_6 |
corosync-vqsim-debuginfo Red Hat:enterprise_linux:9::resilientstorage | All versions | 0:3.1.9-2.el9_6 |
corosynclib-debuginfo Red Hat:enterprise_linux:9::resilientstorage | All versions | 0:3.1.9-2.el9_6 |
corosynclib-devel Red Hat:enterprise_linux:9::resilientstorage | All versions | 0:3.1.9-2.el9_6 |
corosync Rocky Linux:10 | All versions | 0:3.1.9-1.el10_0.1 |
corosync Rocky Linux:9 | All versions | 0:3.1.9-2.el9_6 |
corosync SUSE:Linux Enterprise High Availability Extension 15 SP3 | All versions | 2.4.6-150300.12.13.1 |
corosync SUSE:Linux Enterprise High Availability Extension 15 SP4 | All versions | 2.4.6-150300.12.13.1 |
corosync SUSE:Linux Enterprise High Availability Extension 15 SP5 | All versions | 2.4.6-150300.12.13.1 |
Products include Corosync Corosync.
How do I fix CVE-2025-30472?
Apply the vendor's patch.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2025-30472 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-30472 exists.
Other vulnerabilities in Corosync
Sources
Also known as ALSA-2025:7201, ALSA-2025:7478, AZL-59189, AZL-61774, CLSA-2025-1747251688, DEBIAN-CVE-2025-30472 and 12 more.