MariaDB is a multi-user, multi-threaded SQL database server. For all practical purposes, MariaDB is binary-compatible with MySQL. The following packages have been upgraded to a later upstream version: rh-mariadb105-galera , rh-mariadb105-mariadb . Security Fix: * mariadb: convert_const_to_int use-after-free when the BIGINT data type is used * mariadb: lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer * mariadb: lack of validating the existence of an object prior to performing operations on the object * mariadb: lack of proper validation of a user-supplied string before using it as a format specifier * mariadb: CONNECT storage engine heap-based buffer overflow * mariadb: assertion failure in Item_args::walk_arg * mariadb: use-after-poison when complex conversion is involved in blob * mariadb: crash in create_tmp_table::finalize * mariadb: crash in arg_comparator::compare_real_fixed * mariadb: crash at my_decimal::operator= * mariadb: crash at Field::set_default via specially crafted SQL statements * mariadb: assertion failure via Item_field::used_tables/update_depend_map_for_order * mariadb: use-after-poison in my_strcasecmp_8bit of ctype-simple.c * mariadb: crash via Item_subselect::init_expr_cache_tracker * mariadb: crashe in query_arena::set_query_arena upon SELECT from view * mariadb: assertion failures in decimal_bin_size * mariadb: crash when using HAVING with NOT EXIST predicate in an equality * mariadb: assertion failure in compare_order_elements * mariadb: crash when using HAVING with IS NULL predicate in an equality * mariadb: use-after-poison in Binary_string::free_buffer * mariadb: crash in multi-update and implicit grouping * mariadb: assertion failure in sql/item_func.cc * mariadb: crash via window function in expression in ORDER BY * mariadb: assertion failure in sql/item_cmpfunc.cc * mariadb: use-after-free when WHERE has subquery with an outer reference in HAVING * mariadb: assertion failure in VDec::VDec at /sql/sql_type.cc * mariadb: incorrect key in quot;dup valuequot; error after long unique * mariadb: use-after-poison in Binary_string::free_buffer * mariadb: improper locking in ds_compress.cc * mariadb: improper locking in ds_compress.cc * mariadb: crash at init_expr_cache_tracker * mariadb: crash in cleanup/Item::cleanup_processor * mariadb: crash in fix_outer_field for INSERT SELECT * mariadb: crash in Item_args::walk_args * mariadb: segmentation fault in get_loops/report_use/filesort * mariadb: crash executing query with VIEW, aggregate and subquery * mariadb: crash via an unused common table expression * mariadb: ha_maria::extra crash via certain SELECT statements * mariadb: crash in sub_select_postjoin_aggr for a NULL value of aggr * mariadb: sql_parse.cc crash because of used_tables expectations * mariadb: application crash via long SELECT DISTINCT statements For more details about the security issue, including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page listed in the References section. Bug Fix: * Don"t use less parallelism if not necessary * [Tracker] Rebase to Galera 26.4.11