InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch

I get this crash every once in a while (~4 to 5 days). I can't find find the core dump in my folder.
Looks very similar to #MDEV-29660 but with 11.1.2

Version: '11.1.2-MariaDB-1:11.1.2+maria~ubu2204' socket: '/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
2023-09-12 5:45:33 0 [ERROR] [FATAL] InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch. Please refer to https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/
230912 6:05:04 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 11.1.2-MariaDB-1:11.1.2+maria~ubu2204 source revision: 9bc25d98209df6810f7a7d5e7dd3ae677a313ab5
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=140
max_threads=153
thread_count=114
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 468041 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x0 thread_stack 0x49000
mariadbd(my_print_stacktrace+0x32)[0x55b02f35c7c2]
Printing to addr2line failed
mariadbd(handle_fatal_signal+0x488)[0x55b02ee35cf8]
/lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x7f8640fcf520]
/lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x12c)[0x7f8641023a7c]
/lib/x86_64-linux-gnu/libc.so.6(raise+0x16)[0x7f8640fcf476]
/lib/x86_64-linux-gnu/libc.so.6(abort+0xd3)[0x7f8640fb57f3]
mariadbd(+0x6b1a21)[0x55b02ea41a21]
mariadbd(+0x6a7eea)[0x55b02ea37eea]
mariadbd(_ZN5tpool19thread_pool_generic13timer_generic7executeEPv+0x40)[0x55b02f2f1d20]
mariadbd(_ZN5tpool4task7executeEv+0x3a)[0x55b02f2f27da]
mariadbd(_ZN5tpool19thread_pool_generic11worker_mainEPNS_11worker_dataE+0x57)[0x55b02f2f0867]
/lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253)[0x7f8641378253]
/lib/x86_64-linux-gnu/libc.so.6(+0x94b43)[0x7f8641021b43]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x44)[0x7f86410b2bb4]
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.
Writing a core file...
Working directory at /var/lib/mysql
Resource Limits:
Limit Soft Limit Hard Limit Units
Max cpu time unlimited unlimited seconds
Max file size unlimited unlimited bytes
Max data size unlimited unlimited bytes
Max stack size 8388608 unlimited bytes
Max core file size unlimited unlimited bytes
Max resident set unlimited unlimited bytes
Max processes unlimited unlimited processes
Max open files 1048576 1048576 files
Max locked memory 65536 65536 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 3385 3385 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 0 0
Max realtime priority 0 0
Max realtime timeout unlimited unlimited us
Core pattern: |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %e

Kernel version: Linux version 5.15.0-103.114.4.el8uek.x86_64 (mockbuild@host-100-100-224-28) (gcc (GCC) 11.2.1 20220127 (Red Hat 11.2.1-9.1.0.3), GNU ld version 2.36.1-2.0.1.el8) #2 SMP Mon Jun 26 10:13:01
PDT 2023