UbuntuUpdates.org

Bugs fixes in "corosync"

Origin Bug number Title Date fixed
Launchpad 1911904 corosync locks all its current and future memory 2021-03-30
Launchpad 1911904 corosync locks all its current and future memory 2021-03-30
Launchpad 1918735 fails to start in unprivileged container 2021-03-30
Launchpad 1911904 corosync locks all its current and future memory 2021-03-30
Launchpad 1918735 fails to start in unprivileged container 2021-03-30
Launchpad 1911904 corosync locks all its current and future memory 2021-03-30
Launchpad 1911904 corosync locks all its current and future memory 2021-03-23
Launchpad 1911904 corosync locks all its current and future memory 2021-03-23
Launchpad 1918735 fails to start in unprivileged container 2021-03-23
Launchpad 1911904 corosync locks all its current and future memory 2021-03-23
Launchpad 1918735 fails to start in unprivileged container 2021-03-23
Launchpad 1911904 corosync locks all its current and future memory 2021-03-23
CVE CVE-2018-1084 corosync before version 2.4.4 is vulnerable to an integer overflow in exec/totemcrypto.c. 2019-05-30
CVE CVE-2018-1084 corosync before version 2.4.4 is vulnerable to an integer overflow in exec/totemcrypto.c. 2019-05-30
CVE CVE-2018-1084 corosync before version 2.4.4 is vulnerable to an integer overflow in exec/totemcrypto.c. 2019-05-30
CVE CVE-2018-1084 corosync before version 2.4.4 is vulnerable to an integer overflow in exec/totemcrypto.c. 2019-05-30
CVE CVE-2018-1084 corosync before version 2.4.4 is vulnerable to an integer overflow in exec/totemcrypto.c. 2019-05-30
CVE CVE-2018-1084 corosync before version 2.4.4 is vulnerable to an integer overflow in exec/totemcrypto.c. 2019-05-30
Launchpad 1739033 Corosync: Assertion 'sender_node != NULL' failed when bind iface is ready after corosync boots 2018-01-02
Launchpad 1739033 Corosync: Assertion 'sender_node != NULL' failed when bind iface is ready after corosync boots 2017-12-21



About   -   Send Feedback to @ubuntu_updates