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: mariadb (10.3.32), galera (25.3.34). (BZ#2050543) Security Fix(es): * mysql: Server: DML unspecified vulnerability (CPU Apr 2021) (CVE-2021-2154) * mysql: Server: DML unspecified vulnerability (CPU Apr 2021) (CVE-2021-2166) * mysql: InnoDB unspecified vulnerability (CPU Jul 2021) (CVE-2021-2372) * mysql: InnoDB unspecified vulnerability (CPU Jul 2021) (CVE-2021-2389) * mysql: InnoDB unspecified vulnerability (CPU Oct 2021) (CVE-2021-35604) * mariadb: Integer overflow in sql_lex.cc integer leading to crash (CVE-2021-46667) * mariadb: Crash in get_sort_by_table() in subquery with ORDER BY having outer ref (CVE-2021-46657) * mariadb: save_window_function_values triggers an abort during IN subquery (CVE-2021-46658) * mariadb: Crash in set_var.cc via certain UPDATE queries with nested subqueries (CVE-2021-46662) * mariadb: Crash caused by mishandling of a pushdown from a HAVING clause to a WHERE clause (CVE-2021-46666) * mariadb: No password masking in audit log when using ALTER USER IDENTIFIED BY command (BZ#1981332) 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. Bug Fix(es): * mariadb:10.3/mariadb: /etc/security/user_map.conf getting overwritten with mariadb-server upgrade (BZ#2050514) * MariaDB logrotate leads to "gzip: stdin: file size changed while zipping" (BZ#2050532) * Crash: WSREP: invalid state ROLLED_BACK (FATAL) (BZ#2050533) * Galera doesn't work without 'procps-ng' package MariaDB-10.3 (BZ#2050550)