CVE-2026-133475: Corosync: corosync: heap-based buffer overflow in memb_commit_token handling when msg_len exceeds commit_token_storage

Published Nov 19, 2026
·
Updated

A flaw was found in corosync. The membership commit token handler in exec/totemsrp.c copies a received membcommittoken into a fixed-size heap buffer (committokenstorage[40000]) using the full received message length (msglen). checkmembcommittokensanity() only validates lower bounds (minimum header size and space for addrentries) and caps addrentries at PROCESSORCOUNTMAX; it does not reject messages larger than committokenstorage. A crafted commit token with a valid small address list and trailing padding above 40000 bytes can therefore overflow the heap-allocated totemsrpinstance when a node is in MEMBSTATEGATHER and the token matches membership and ring-sequence gates. Over knet, messages can be up to the default 64 KiB netmtu, allowing roughly 24 KiB of attacker-controlled out-of-bounds write. This is distinct from CVE-2026-35091 (incorrect success return on truncated messages) and CVE-2026-81666 (32-bit integer overflow in requiredlen). Impact is heap memory corruption and denial of service of the Corosync daemon; code execution was not demonstrated. Reported via PSIRTSUPT-30664 by Adam Bedard. Upstream maintainer Jan Friesse confirmed the issue and provided a proposed fix that adds an upper-bound length check and moves alloca after the sanity check.

Other sources

A heap-based buffer overflow was found in Corosync's Totem SRP membership commit token handling. The sanity check for membcommittoken messages validates only minimum length and address-entry counts, not an upper bound against the fixed committokenstorage buffer. A network-adjacent attacker who can deliver a crafted oversized commit token to a node in the GATHER membership state may overflow the heap-allocated totemsrp instance, leading to memory corruption and denial of service.

— MITRE

Affected Software

1 affected component
corosync corosync

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    In Corosync's memb_commit_token handling, reject messages with msg_len greater than the 40000-byte commit_token_storage buffer, and move alloca after the sanity check.

Event History

Nov 19, 2026
Data Sourced
via Red Hat·09:38 PM
DescriptionSeverityAffected Software
Nov 20, 2026
CVE Published
via MITRE·05:47 PM
Data Sourced
via MITRE·05:47 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:18 PM
DescriptionSeverityWeakness

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203