Register | Log in

corosync

cluster engine daemon and utilities

Choose email to subscribe with

general

source: corosync (main)
version: 3.1.10-2
maintainer: Debian HA Maintainers (archive) (DMD)
uploaders: Adrian Vondendriesch [DMD] – Ferenc Wágner [DMD]
arch: all any
std-ver: 4.7.4
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 3.1.2-2
o-o-sec: 3.1.2-2+deb11u1
oldstable: 3.1.7-1+deb12u1
stable: 3.1.9-2
testing: 3.1.10-1
unstable: 3.1.10-2

versioned links

3.1.2-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.1.2-2+deb11u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.1.7-1+deb12u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.1.9-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.1.10-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.1.10-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

corosync
corosync-doc
corosync-notifyd
corosync-vqsim
libcfg-dev
libcfg7
libcmap-dev
libcmap4
libcorosync-common-dev
libcorosync-common4
libcpg-dev
libcpg4
libquorum-dev
libquorum5
libsam-dev
libsam4
libvotequorum-dev
libvotequorum8

action needed

2 security issues in trixie high

There are 2 open security issues in trixie.

2 important issues:

CVE-2026-35091: A flaw was found in Corosync. A remote unauthenticated attacker can exploit a wrong return value vulnerability in the Corosync membership commit token sanity check by sending a specially crafted User Datagram Protocol (UDP) packet. This can lead to an out-of-bounds read, causing a denial of service (DoS) and potentially disclosing limited memory contents. This vulnerability affects Corosync when running in totemudp/totemudpu mode, which is the default configuration.
CVE-2026-35092: A flaw was found in Corosync. An integer overflow vulnerability in Corosync's join message sanity validation allows a remote, unauthenticated attacker to send crafted User Datagram Protocol (UDP) packets. This can cause the service to crash, leading to a denial of service. This vulnerability specifically affects Corosync deployments configured to use totemudp/totemudpu mode.

Created: 2026-04-02 Last update: 2026-05-03 23:30

2 security issues in forky high

There are 2 open security issues in forky.

2 important issues:

CVE-2026-35091: A flaw was found in Corosync. A remote unauthenticated attacker can exploit a wrong return value vulnerability in the Corosync membership commit token sanity check by sending a specially crafted User Datagram Protocol (UDP) packet. This can lead to an out-of-bounds read, causing a denial of service (DoS) and potentially disclosing limited memory contents. This vulnerability affects Corosync when running in totemudp/totemudpu mode, which is the default configuration.
CVE-2026-35092: A flaw was found in Corosync. An integer overflow vulnerability in Corosync's join message sanity validation allows a remote, unauthenticated attacker to send crafted User Datagram Protocol (UDP) packets. This can cause the service to crash, leading to a denial of service. This vulnerability specifically affects Corosync deployments configured to use totemudp/totemudpu mode.

Created: 2026-04-02 Last update: 2026-05-03 23:30

2 security issues in bullseye high

There are 2 open security issues in bullseye.

2 important issues:

CVE-2026-35091: A flaw was found in Corosync. A remote unauthenticated attacker can exploit a wrong return value vulnerability in the Corosync membership commit token sanity check by sending a specially crafted User Datagram Protocol (UDP) packet. This can lead to an out-of-bounds read, causing a denial of service (DoS) and potentially disclosing limited memory contents. This vulnerability affects Corosync when running in totemudp/totemudpu mode, which is the default configuration.
CVE-2026-35092: A flaw was found in Corosync. An integer overflow vulnerability in Corosync's join message sanity validation allows a remote, unauthenticated attacker to send crafted User Datagram Protocol (UDP) packets. This can cause the service to crash, leading to a denial of service. This vulnerability specifically affects Corosync deployments configured to use totemudp/totemudpu mode.

Created: 2026-04-02 Last update: 2026-05-03 23:30

2 security issues in bookworm high

There are 2 open security issues in bookworm.

2 important issues:

CVE-2026-35091: A flaw was found in Corosync. A remote unauthenticated attacker can exploit a wrong return value vulnerability in the Corosync membership commit token sanity check by sending a specially crafted User Datagram Protocol (UDP) packet. This can lead to an out-of-bounds read, causing a denial of service (DoS) and potentially disclosing limited memory contents. This vulnerability affects Corosync when running in totemudp/totemudpu mode, which is the default configuration.
CVE-2026-35092: A flaw was found in Corosync. An integer overflow vulnerability in Corosync's join message sanity validation allows a remote, unauthenticated attacker to send crafted User Datagram Protocol (UDP) packets. This can cause the service to crash, leading to a denial of service. This vulnerability specifically affects Corosync deployments configured to use totemudp/totemudpu mode.

Created: 2026-04-02 Last update: 2026-05-03 23:30

1 open merge request in Salsa normal

There is 1 open merge request for this package on Salsa. You should consider reviewing and/or merging these merge requests.

Created: 2026-05-03 Last update: 2026-05-03 18:35

debian/patches: 8 patches to forward upstream low

Among the 8 debian patches available in version 3.1.10-2 of the package, we noticed the following issues:

8 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2026-05-04 08:32

testing migrations

excuses:
- Migration status for corosync (3.1.10-1 to 3.1.10-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- ∙ ∙ Autopkgtest for corosync: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, ppc64el: Test triggered, riscv64: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for corosync-qdevice: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, ppc64el: Test triggered, riscv64: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for dlm: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, ppc64el: Test triggered, riscv64: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for fence-agents: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, ppc64el: Test triggered, riscv64: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for gfs2-utils: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, ppc64el: Test triggered, riscv64: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for ocfs2-tools: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, ppc64el: Test triggered, riscv64: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for pacemaker: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, ppc64el: Test triggered, riscv64: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for prometheus-hacluster-exporter: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, ppc64el: Test triggered, riscv64: Test triggered, s390x: Test triggered
- ∙ ∙ Autopkgtest for sbd: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, ppc64el: Test triggered, riscv64: Test triggered, s390x: Test triggered
- ∙ ∙ Lintian check waiting for test results on riscv64 - info
- ∙ ∙ Too young, only 0 of 5 days old
- Additional info (not blocking):
- ∙ ∙ Updating corosync will fix bugs in testing: #1133837, #1133838
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/c/corosync.html
- ∙ ∙ Reproducibility check waiting for results on amd64
- ∙ ∙ Reproducibility check waiting for results on arm64
- ∙ ∙ Reproducibility check waiting for results on armhf
- ∙ ∙ Reproducibility check waiting for results on i386
- ∙ ∙ Reproducibility check waiting for results on ppc64el
- Not considered

news

[2026-05-03] Accepted corosync 3.1.10-2 (source) into unstable (Ferenc Wágner)
[2026-02-24] corosync 3.1.10-1 MIGRATED to testing (Debian testing watch)
[2026-02-21] Accepted corosync 3.1.10-1 (source) into unstable (Ferenc Wágner)
[2025-09-22] Accepted corosync 3.1.2-2+deb11u1 (source) into oldoldstable-security (Thorsten Alteholz)
[2025-07-08] corosync 3.1.9-2 MIGRATED to testing (Debian testing watch)
[2025-06-21] Accepted corosync 3.1.7-1+deb12u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Moritz Mühlenhoff)
[2025-06-21] Accepted corosync 3.1.9-2 (source) into unstable (Ferenc Wágner)
[2025-03-06] corosync 3.1.9-1 MIGRATED to testing (Debian testing watch)
[2025-03-02] Accepted corosync 3.1.9-1 (source) into unstable (Ferenc Wágner)
[2024-07-23] corosync 3.1.8-3 MIGRATED to testing (Debian testing watch)
[2024-07-20] Accepted corosync 3.1.8-3 (source) into unstable (Ferenc Wágner)
[2024-05-28] corosync 3.1.8-2 MIGRATED to testing (Debian testing watch)
[2024-05-26] Accepted corosync 3.1.8-2 (source) into unstable (Ferenc Wágner)
[2024-05-26] Accepted corosync 3.1.8-1 (source) into unstable (Ferenc Wágner)
[2023-01-19] corosync 3.1.7-1 MIGRATED to testing (Debian testing watch)
[2023-01-15] Accepted corosync 3.1.7-1 (source) into unstable (Ferenc Wágner)
[2022-03-09] corosync 3.1.6-2 MIGRATED to testing (Debian testing watch)
[2022-03-06] Accepted corosync 3.1.6-2 (source) into unstable (Ferenc Wágner)
[2021-11-25] corosync 3.1.6-1 MIGRATED to testing (Debian testing watch)
[2021-11-22] Accepted corosync 3.1.6-1 (source) into unstable (Ferenc Wágner)
[2021-10-13] corosync 3.1.5-2 MIGRATED to testing (Debian testing watch)
[2021-10-13] corosync 3.1.5-2 MIGRATED to testing (Debian testing watch)
[2021-10-01] Accepted corosync 3.1.5-2 (source) into unstable (Ferenc Wágner)
[2021-09-30] Accepted corosync 3.1.5-1 (source) into unstable (Ferenc Wágner)
[2021-07-14] corosync 3.1.2-2 MIGRATED to testing (Debian testing watch)
[2021-07-05] Accepted corosync 3.1.2-2 (source) into unstable (Ferenc Wágner)
[2021-04-17] corosync 3.1.2-1 MIGRATED to testing (Debian testing watch)
[2021-04-07] Accepted corosync 3.1.2-1 (source) into unstable (Ferenc Wágner)
[2021-04-03] Accepted corosync 3.1.1-1 (source) into unstable (Ferenc Wágner)
[2021-03-10] corosync 3.1.0-3 MIGRATED to testing (Debian testing watch)

1
2

bugs [bug history graph]

all: 0

links

homepage
lintian
buildd: logs, reproducibility, cross
popcon
browse source code
other distros
security tracker
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 3.1.9-2ubuntu3
patches for 3.1.9-2ubuntu3

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers

Report problems to the tracker.debian.org pseudo-package in the Debian BTS.

Documentation — Bugs — Git Repository — Contributing