RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

MariaDB upstream plan to make the 5.5.68 release the last release before 5.5 EOL.

We plan to rebase to that version, once it will be released.
That means this update will cover of CVEs fixed by upstream.

---

This is a tracker bug.
It should have set "DEPENDS ON:" against all other Bugzilla tickets which will be part of the update.

DOCS notes:

MariaDB 5.5.66: https://mariadb.com/kb/en/mariadb-5566-release-notes/
MariaDB 5.5.67: https://mariadb.com/kb/en/mariadb-5567-release-notes/
MariaDB 5.5.68: https://mariadb.com/kb/en/mariadb-5568-release-notes/

All three are "maintenance releases", which means there are no new features expected and the focus lies on fixing of the known issues.
I went through the changelogs and haven't find any significant enhancement.

I picked up fixes which I deem significant:
  https://jira.mariadb.org/browse/MDEV-15955
  https://jira.mariadb.org/browse/MDEV-20495
  https://jira.mariadb.org/browse/MDEV-13172
  https://jira.mariadb.org/browse/MDEV-21343
  https://github.com/MariaDB/server/commit/49b9ce15ef
  https://github.com/MariaDB/server/commit/4d1c1b23e1
  https://jira.mariadb.org/browse/MDEV-10466
  https://github.com/MariaDB/server/commit/39c60116e8
  https://github.com/MariaDB/server/commit/6a31aea5a1

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: mariadb security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:4026