MariaDB has released versions 11.8.6, 11.4.10, 10.11.16, and 10.6.25, which include crucial patches for InnoDB crash scenarios, particularly those caused by commands like TRUNCATE and OPTIMIZE. The update enhances Galera clusters by introducing a new GCS protocol version that prevents mixed-version nodes and resolves SST/IST loops, while also fixing permission issues related to the mariadb-dump command on Unix systems. Users are advised to back up their data, check directory permissions, ensure all Galera nodes are updated together, and run mysql_upgrade post-installation to address potential incompatibilities. Additionally, while many bugs have been fixed, users should remain vigilant regarding issues with compressed tables, encryption threads, and large join queries

MariaDB 11.8.6, 11.4.10, 10.11.16, and 10.6.25 released

MariaDB 11.8.6 (and its 11.4, 10.11, 10.6 counterparts) patches several InnoDB crash scenarios—especially those triggered by TRUNCATE, OPTIMIZE and buffer‑pool underruns—so servers that have seen “out‑of‑bounds write” or checksum errors should upgrade immediately. Galera clusters get a new GCS protocol version, which blocks mixed‑version nodes and resolves SST/IST loops that previously filled disks. On Unix systems the mariadb-dump --dir permission check is fixed, eliminating “permission denied” failures when dump processes run under different OS users. Follow the backup‑first checklist, bump all cluster nodes together, and run mysql_upgrade; after that your instance should stay up and stop spitting out those obscure crash logs.

MariaDB 11.8.6, 11.4.10, 10.11.16, and 10.6.25 released @ Linux Compatible