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

This is possibly related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1110254

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

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: 0x7f4b1c000c68
2025-08-02 19:39:32 0 [Note] /usr/sbin/mariadbd (initiated by: unknown): Normal shutdown
stack_bottom = 0x7f4b5412a000 thread_stack 0x49000
2025-08-02 19:39:32 346 [Warning] Aborted connection 346 to db: 'unconnected' user: 'unauthenticated' host: 'x.x.x.x' (This connection closed normally without authentication)
2025-08-02 19:39:32 345 [Warning] Aborted connection 345 to db: 'unconnected' user: 'unauthenticated' host: 'x.x.x.x' (This connection closed normally without authentication)
/usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x556a6c3fc2ee]
/usr/sbin/mariadbd(handle_fatal_signal+0x1a3)[0x556a6bedada3]
libc_sigaction.c:0(__restore_rt)[0x7f4c0105b050]
/lib/x86_64-linux-gnu/libcrypto.so.3(+0x337d09)[0x7f4c01537d09]
/lib/x86_64-linux-gnu/libcrypto.so.3(OSSL_STORE_load+0x106)[0x7f4c014b0b36]
/lib/x86_64-linux-gnu/libcrypto.so.3(+0x2c0271)[0x7f4c014c0271]
/lib/x86_64-linux-gnu/libcrypto.so.3(+0x2c043d)[0x7f4c014c043d]
/lib/x86_64-linux-gnu/libcrypto.so.3(X509_STORE_CTX_get_by_subject+0xeb)[0x7f4c014dc1fb]
/lib/x86_64-linux-gnu/libcrypto.so.3(X509_STORE_CTX_get1_issuer+0x6a)[0x7f4c014dca6a]
/lib/x86_64-linux-gnu/libcrypto.so.3(+0x2e0e87)[0x7f4c014e0e87]
/lib/x86_64-linux-gnu/libcrypto.so.3(+0x2e2ad6)[0x7f4c014e2ad6]
/lib/x86_64-linux-gnu/libcrypto.so.3(X509_verify_cert+0xbc)[0x7f4c014e3bac]
/lib/x86_64-linux-gnu/libssl.so.3(+0x72016)[0x7f4c018c1016]
/lib/x86_64-linux-gnu/libssl.so.3(+0x75fd5)[0x7f4c018c4fd5]
/lib/x86_64-linux-gnu/libssl.so.3(+0x668ff)[0x7f4c018b58ff]
/usr/sbin/mariadbd(+0xc3b7b7)[0x556a6c06f7b7]
/usr/sbin/mariadbd(+0x7c25f6)[0x556a6bbf65f6]
/usr/sbin/mariadbd(+0x7c2ffe)[0x556a6bbf6ffe]
/usr/sbin/mariadbd(+0x79dce9)[0x556a6bbd1ce9]
/usr/sbin/mariadbd(+0x79f709)[0x556a6bbd3709]
/usr/sbin/mariadbd(_Z16acl_authenticateP3THDj+0x38e)[0x556a6bbf7e5e]
/usr/sbin/mariadbd(+0x977785)[0x556a6bdab785]
/usr/sbin/mariadbd(_Z16login_connectionP3THD+0x40)[0x556a6bdab910]
/usr/sbin/mariadbd(_Z22thd_prepare_connectionP3THD+0x1b)[0x556a6bdac26b]
/usr/sbin/mariadbd(_Z24do_handle_one_connectionP7CONNECTb+0x362)[0x556a6bdaca12]
/usr/sbin/mariadbd(handle_one_connection+0x5d)[0x556a6bdacd8d]
/usr/sbin/mariadbd(+0xcd9ee7)[0x556a6c10dee7]
nptl/pthread_create.c:442(start_thread)[0x7f4c010a81f5]
x86_64/clone3.S:83(clone3)[0x7f4c0112889c]


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

There hasn't been any updates in MariaDB, but OpenSSL recently updated
in Bookworm. This is for sure a regression in recent OpenSSL update,
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1110254

Seems this was fixed in OpenSSL/3.0.17-1~deb12u2