[From nobody Sun May  3 20:37:07 2026
Received: (at submit) by bugs.debian.org; 14 Apr 2026 18:39:14 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-11.0 required=4.0 tests=BAYES_00,FROMDEVELOPER,
 MD5_SHA1_SUM,NO_RELAYS,XMAILER_REPORTBUG autolearn=ham
 autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 13; hammy, 148; neutral, 41; spammy,
 2. spammytokens:0.942-+--H*r:bugs.debian.org, 0.909-+--limited
 hammytokens:0.000-+--H*F:U*carnil, 0.000-+--XDebbugsCc,
 0.000-+--X-Debbugs-Cc, 0.000-+--HTo:N*Debian, 0.000-+--H*Ad:N*Bug
Return-path: <carnil@debian.org>
Received: via submission by buxtehude.debian.org with esmtp (Exim 4.96)
 (envelope-from <carnil@debian.org>) id 1wCifJ-0069td-1h
 for submit@bugs.debian.org; Tue, 14 Apr 2026 18:39:14 +0000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Salvatore Bonaccorso <carnil@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: corosync: CVE-2026-35091
Message-ID: <177619195250.217850.8604177597628379477.reportbug@eldamar.lan>
X-Mailer: reportbug 13.2.0
Date: Tue, 14 Apr 2026 20:39:12 +0200
Delivered-To: submit@bugs.debian.org

Source: corosync
Version: CVE-2026-35092
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: carnil@debian.org, Debian Security Team <team@security.debian.org>

Hi,

The following vulnerability was published for corosync.

CVE-2026-35091[0]:
| 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.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2026-35091
    https://www.cve.org/CVERecord?id=CVE-2026-35091
[1] https://github.com/corosync/corosync/commit/a16614accfdb3481264d7281843fadf439d9ab1b

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
]