Bug 2524910 (CVE-2026-81665) - CVE-2026-81665 corosync: corosync: heap-based buffer overflow in totempg assembly buffer during fragmented message reassembly
Summary: CVE-2026-81665 corosync: corosync: heap-based buffer overflow in totempg asse...
Keywords:
Status: NEW
Alias: CVE-2026-81665
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2528437
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-27 10:44 UTC by OSIDB Bzimport
Modified: 2026-10-02 13:10 UTC (History)
18 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:67872 0 None None None 2026-09-16 09:16:50 UTC
Red Hat Product Errata RHSA-2026:67873 0 None None None 2026-09-16 11:10:06 UTC
Red Hat Product Errata RHSA-2026:67878 0 None None None 2026-09-16 09:23:57 UTC
Red Hat Product Errata RHSA-2026:67879 0 None None None 2026-09-16 12:29:02 UTC
Red Hat Product Errata RHSA-2026:67880 0 None None None 2026-09-16 08:51:47 UTC
Red Hat Product Errata RHSA-2026:67881 0 None None None 2026-09-16 10:24:43 UTC
Red Hat Product Errata RHSA-2026:68574 0 None None None 2026-09-17 09:13:34 UTC
Red Hat Product Errata RHSA-2026:69277 0 None None None 2026-09-21 14:26:14 UTC
Red Hat Product Errata RHSA-2026:69278 0 None None None 2026-09-21 11:22:52 UTC
Red Hat Product Errata RHSA-2026:69279 0 None None None 2026-09-21 11:18:10 UTC
Red Hat Product Errata RHSA-2026:69280 0 None None None 2026-09-21 11:15:57 UTC

Description OSIDB Bzimport 2026-08-27 10:44:31 UTC
Corosync is a group communication system providing reliable ordered messaging and membership services, and is the communication layer underlying Pacemaker HA clusters (RHEL High Availability Add-On). In exec/totempg.c, the totempg_deliver_fn function reassembles fragmented multicast messages into a fixed-size per-node assembly buffer (struct assembly, data[MESSAGE_SIZE_MAX + KNET_MAX_PACKET_SIZE], ~1.06 MB on normal builds, ~128 KB on small-memory-footprint builds). The only bounds check before the memcpy at line 663 is an assert() at line 662, which is compiled out in release builds (-DNDEBUG). assembly->index grows unboundedly at line 737 for each continuation fragment with no upper-bound check. After 17-18 fragments on normal builds (3 fragments on small-memory-footprint builds), the memcpy writes attacker-controlled data past the end of the heap buffer.

Verified via an ASan-instrumented standalone harness reproducing the exact buffer layout and memcpy/index logic: after 17 fragments of 65,481 bytes each, assembly->index reached 1,113,177 (buffer capacity 1,114,112); fragment 18 triggered a confirmed heap-buffer-overflow WRITE of 65,481 bytes, 64,546 bytes past the buffer end.

Present in corosync v3.1.10 (latest upstream release) and main HEAD (commit 65235a8); no upstream fix exists for this bug. Reported by Tristan Madani (Talence Security) via PSIRTSUPT-22352.

Comment 1 Jon Orris 2026-09-16 08:51:45 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions

Via RHSA-2026:67880 https://access.redhat.com/errata/RHSA-2026:67880

Comment 2 Jon Orris 2026-09-16 09:16:49 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:67872 https://access.redhat.com/errata/RHSA-2026:67872

Comment 3 Jon Orris 2026-09-16 09:23:55 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions

Via RHSA-2026:67878 https://access.redhat.com/errata/RHSA-2026:67878

Comment 4 Jon Orris 2026-09-16 10:24:41 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10.0 Extended Update Support

Via RHSA-2026:67881 https://access.redhat.com/errata/RHSA-2026:67881

Comment 5 Jon Orris 2026-09-16 11:10:04 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:67873 https://access.redhat.com/errata/RHSA-2026:67873

Comment 6 Jon Orris 2026-09-16 12:29:00 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.6 Extended Update Support

Via RHSA-2026:67879 https://access.redhat.com/errata/RHSA-2026:67879

Comment 7 Jon Orris 2026-09-17 09:13:33 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7 Extended Lifecycle Support

Via RHSA-2026:68574 https://access.redhat.com/errata/RHSA-2026:68574

Comment 8 Jon Orris 2026-09-21 11:15:55 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support
  Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On

Via RHSA-2026:69280 https://access.redhat.com/errata/RHSA-2026:69280

Comment 9 Jon Orris 2026-09-21 11:18:09 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support
  Red Hat Enterprise Linux 8.6 Extended Update Support Long-Life Add-On

Via RHSA-2026:69279 https://access.redhat.com/errata/RHSA-2026:69279

Comment 10 Jon Orris 2026-09-21 11:22:50 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions
  Red Hat Enterprise Linux 8.8 Telecommunications Update Service

Via RHSA-2026:69278 https://access.redhat.com/errata/RHSA-2026:69278

Comment 11 Jon Orris 2026-09-21 14:26:13 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:69277 https://access.redhat.com/errata/RHSA-2026:69277


Note You need to log in before you can comment on or make changes to this bug.