[debian-mysql] Bug#1110216: MariaDB crashes after upgrade to openssl=3.0.17-1~deb12u1

[Martin Pöthig]

Package: mariadb-server

Version: 1:10.11.11-0+deb12u1

After upgrading to  openssl=3.0.17-1~deb12u1 on Debian Bookworm, MariaDB Server with server-side TLS crashes with various error messages.

I needed to kill the process and restart the service and this happens repeatedly after several minutes.

These issues do not occur after downgrading to openssl=3.0.16-1~deb12u1

2025-08-01  5:10:56 0 [Note] InnoDB: Buffer pool(s) load completed at 250801  5:10:56
double free or corruption (out)
250801  5:10:57 [ERROR] /usr/sbin/mariadbd got signal 11 ;
Fatal signal 6 while backtracing
Sorry, we probably made a mistake, and this is a bug.

Your assistance in bug reporting will enable us to fix this for the next release.
To report this bug, see https://mariadb.com/kb/en/reporting-bugs about how to report
a bug on https://jira.mariadb.org/.

Please include the information from the server start above, to the end of the
information below.

Server version: 10.11.11-MariaDB-0+deb12u1-log source revision: e69f8cae1a15e15b9e4f5e0f8497e1f17bdc81a4

The information page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/
contains instructions to obtain a better version of the backtrace below.
Following these instructions will help MariaDB developers provide a fix quicker.

Attempting backtrace. Include this in the bug report.
(note: Retrieving this information may fail)

Thread pointer: 0x7fee8c000c68


Version: '10.11.11-MariaDB-0+deb12u1-log'  socket: '/run/mysqld/mysqld.sock'  port: 3306  Debian 12
2025-08-01  5:11:03 0 [Note] InnoDB: Buffer pool(s) load completed at 250801  5:11:03
2025-08-01  5:41:32 0 [Note] InnoDB: Memory pressure event freed 11595 pages
2025-08-01  6:00:10 0 [Note] InnoDB: Memory pressure event freed 929 pages
2025-08-01  6:03:41 0 [Note] InnoDB: Memory pressure event freed 79006 pages
malloc(): unsorted double linked list corrupted
250801  7:56:36 [ERROR] /usr/sbin/mariadbd got signal 6 ;
Sorry, we probably made a mistake, and this is a bug.

Your assistance in bug reporting will enable us to fix this for the next release.
To report this bug, see https://mariadb.com/kb/en/reporting-bugs about how to report
a bug on https://jira.mariadb.org/.

Please include the information from the server start above, to the end of the
information below.

Server version: 10.11.11-MariaDB-0+deb12u1-log source revision: e69f8cae1a15e15b9e4f5e0f8497e1f17bdc81a4

The information page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/
contains instructions to obtain a better version of the backtrace below.
Following these instructions will help MariaDB developers provide a fix quicker.

Attempting backtrace. Include this in the bug report.
(note: Retrieving this information may fail)

Thread pointer: 0x7fd928000c68
stack_bottom = 0x7fd9d010d000 thread_stack 0x49000


Pleaset let me know if I can share any additional information.

Thank you and kind regards,
Martin Pöthig


XIMA MEDIA GmbH
Sudhausweg 9
01099 Dresden

Geschäftsführung:  Sascha Tom Weber, Samer Habib
Handelsregister:  Amtsgericht Dresden (HRB-Nr. 16098), Sitz der Gesellschaft: Dresden
USt-IdNr.:  DE 195 031 875
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-mysql-maint/attachments/20250801/52257985/attachment-0001.htm>