If crypto is disabled in corosync/knet (this is not a supported configuration), then corosync can be crashed by a malformed acket sent from another node in a running cluster.

Supported installations are immune to this bug, If crypto is enabled then the packet will not decrypt correctly and decompression will not be attempted.

for reproducer see https://github.com/kronosnet/kronosnet/issues/435

This issue is patched upstream as

https://github.com/kronosnet/kronosnet/pull/437