MariaDB 10.6.25 crashes with signal 11 when executing stored procedure showing Status: KILL_SERVER

MariaDB server crashes repeatedly with signal 11 (segmentation fault) while executing a stored procedure. The crash terminates the server process, and mysqld_safe automatically restarts it.

The issue occurs when executing the stored procedure:

CALL Alert_PI_IR_DiscDate(...)

The server does not return an SQL error; instead, it crashes, indicating a potential internal MariaDB bug.

MariaDB Config
[mysqld1]
datadir=/mnt/data/abc/data
tmpdir=/mnt/data/abc/tmp
log_error=/mnt/data/abc/logs/error/abc_db.err
socket=/mnt/data/abc/abc.sock
pid-file=/mnt/data/abc/abc.pid
character-set-client-handshake = FALSE
character-set-server = latin1
collation-server = latin1_general_ci
init_connect = 'SET collation_connection = latin1_general_ci;'
lower_case_table_names=1
innodb_buffer_pool_size=80G
innodb_log_file_size=6G
innodb_flush_log_at_trx_commit=2
max_allowed_packet=1024M
table_definition_cache=4000
port=3333
user=mysql
sort_buffer_size=4M
join_buffer_size=4M
max_heap_table_size=5G
tmp_table_size=5G
max_connections=400
max_sp_recursion_depth=255
slow-query-log=1
slow-query-log-file=/mnt/data/abc/logs/query/abc_slow_query_log.txt
long-query-time=1
query_cache_size=0
plugin_load_add=ha_connect.so
transaction-isolation=READ-COMMITTED
back_log=260
skip-name-resolve
open_files_limit=1048576

Expected Behavior

MariaDB should handle the query safely and either:

Execute successfully, or
Return a SQL error if the query is invalid or resource-intensive

The server should not crash under any circumstances.

Actual Behavior
MariaDB process crashes with signal 11
Server shuts down abruptly
Automatic restart occurs via mysqld_safe
Application experiences disruption