This bug was fixed in the package mariadb-10.5 -
1:10.5.15-0ubuntu0.21.10.1
---------------
mariadb-10.5 (1:10.5.15-0ubuntu0.21.10.1) impish-security; urgency=medium
* SECURITY UPDATE: New upstream version 10.5.15 includes fixes for the
following security vulnerabilities (LP: #1961350):
- CVE-2021-46661
- CVE-2021-46663
- CVE-2021-46664
- CVE-2021-46665
- CVE-2021-46668
* New upstream version 10.5.14. Includes security fixes for
- CVE-2021-46659
- CVE-2022-24048
- CVE-2022-24050
- CVE-2022-24051
- CVE-2022-24052
* Notable upstream functional changes in 10.5.14:
- New default value for innodb_change_buffering is 'none' instead of old
value 'all' (MDEV-27734). This change should improve crash safety but
might cause performance regressions on systems that use old spinning disks
(HDD) where seek latency is higher.
- New default minimum value for innodb_buffer_pool_size is 20 MB (from 2 MB)
-- Otto Kekäläinen <o...@debian.org> Thu, 17 Feb 2022 18:27:55 -0800
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961350
Title:
CVE-2022-24048 et al affect MariaDB in Ubuntu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1961350/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
