split_materialized: SIGSEGV in best_access_path()

Some history:
We have had issues with this server for a while. The issues are only present on the replica, the master runs fine.

Up until last week the two servers ran the same Debian and MariaDB version, as well as config. Last week we rebuilt the server, going from Debian 11 and MariaDB 10.6.7 to Debian 12 and MariaDB 10.11.4.

We had 6 segfaults on the replica, the following is the shortened log of this, more complete logs in attachment. (I removed some noise form leftover partitions, hostnames and the queries, its the same query in all five instances and it might be relevant but also sensitive for our customer, let me know if needed and i will upload the complete error.log to ftp)

231030 10:54:21 [ERROR] mysqld got signal 11 ;
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.

231030 10:56:16 [ERROR] mysqld got signal 11 ;
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.

231030 11:01:57 [ERROR] mysqld got signal 11 ;
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.

231030 11:06:05 [ERROR] mysqld got signal 11 ;
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.

231030 13:36:02 [ERROR] mysqld got signal 11 ;
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.

231030 13:37:38 [ERROR] mysqld got signal 11 ;
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.

These segfaults broke replication and we had to manually fix records from binlog as the total datasize is too large to clone in a reasonable amount of time.

Please let me know if there is more information i can provide. We dont have core dump from these crashes as it was not enabled in the config, it is now tho. If needed i should be able to provide more debug on the next crash.
Im not experienced in debugging applications so i might need some guidance, i have however read up on how to perform a backtrace etc.