ALSA-2022:5948

MariaDB is a multi-user, multi-threaded SQL database server that is binary compatible with MySQL. The following packages have been upgraded to a later upstream version: galera (26.4.11), mariadb (10.5.16), mysql-selinux (1.0.5). Security Fix(es): * mariadb: MariaDB through 10.5.9 allows attackers to trigger a convertconsttoint use-after-free when the BIGINT data type is used (CVE-2021-46669) * mariadb: lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer (CVE-2022-24048) * mariadb: lack of validating the existence of an object prior to performing operations on the object (CVE-2022-24050) * mariadb: lack of proper validation of a user-supplied string before using it as a format specifier (CVE-2022-24051) * mariadb: CONNECT Storage Engine Heap-based Buffer Overflow Privilege Escalation Vulnerability (CVE-2022-24052) * mariadb: assertion failure in Itemargs::walkarg (CVE-2022-27376) * mariadb: use-after-poison when complex conversion is involved in blob (CVE-2022-27377) * mariadb: server crash in createtmptable::finalize (CVE-2022-27378) * mariadb: server crash in component argcomparator::comparerealfixed (CVE-2022-27379) * mariadb: server crash at mydecimal::operator= (CVE-2022-27380) * mariadb: server crash at Field::setdefault via specially crafted SQL statements (CVE-2022-27381) * mariadb: assertion failure via component Itemfield::usedtables/updatedependmapfororder (CVE-2022-27382) * mariadb: use-after-poison in mystrcasecmp8bit() of ctype-simple.c (CVE-2022-27383) * mariadb: crash via component Itemsubselect::initexprcachetracker (CVE-2022-27384) * mariadb: server crashes in queryarena::setqueryarena upon SELECT from view (CVE-2022-27386) * mariadb: assertion failures in decimalbinsize (CVE-2022-27387) * mariadb: crash when using HAVING with NOT EXIST predicate in an equality (CVE-2022-27444) * mariadb: assertion failure in compareorderelements (CVE-2022-27445) * mariadb: crash when using HAVING with IS NULL predicate in an equality (CVE-2022-27446) * mariadb: use-after-poison in Binarystring::freebuffer (CVE-2022-27447) * mariadb: crash in multi-update and implicit grouping (CVE-2022-27448) * mariadb: assertion failure in sql/itemfunc.cc (CVE-2022-27449) * mariadb: crash via window function in expression in ORDER BY (CVE-2022-27451) * mariadb: assertion failure in sql/itemcmpfunc.cc (CVE-2022-27452) * mariadb: use-after-free when WHERE has subquery with an outer reference in HAVING (CVE-2022-27455) * mariadb: assertion failure in VDec::VDec at /sql/sqltype.cc (CVE-2022-27456) * mariadb: incorrect key in "dup value" error after long unique (CVE-2022-27457) * mariadb: use-after-poison in Binarystring::freebuffer (CVE-2022-27458) * mariadb: improper locking due to the unreleased lock in extra/mariabackup/dscompress.cc (CVE-2022-31622) * mariadb: improper locking due to the unreleased lock in extra/mariabackup/dscompress.cc (CVE-2022-31623) * mariadb: Crash executing query with VIEW, aggregate and subquery (CVE-2021-46659) * mariadb: MariaDB allows an application crash in findfieldintables and findorderinlist via an unused common table expression (CTE) (CVE-2021-46661) * mariadb: MariaDB through 10.5.13 allows a hamaria::extra application crash via certain SELECT statements (CVE-2021-46663) * mariadb: MariaDB through 10.5.9 allows an application crash in subselectpostjoinaggr for a NULL value of aggr (CVE-2021-46664) * mariadb: MariaDB through 10.5.9 allows a sqlparse.cc application crash because of incorrect usedtables expectations (CVE-2021-46665) * mariadb: MariaDB through 10.5.9 allows an application crash via certain long SELECT DISTINCT statements (CVE-2021-46668) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.