Buffer overflow during insert

After Mariadb is updated from 10.4.12 to 10.4.13, I ran sysbench this test :

sysbench /usr/share/sysbench/oltp_read_write.lua --threads=80 --events=0 --time=300 --mysql-host=127.0.0.1 --mysql-db=sbtest --mysql-user=root --mysql-password=xxx--mysql-port=3306 --tables=20 --delete_inserts=20 --index_updates=20 --non_index_updates=20 --table-size=1000000 --db-ps-mode=disable --report-interval=1 run

There are a lot of conflicts and on the last Insert it just crashes

(wsrep::unique_lock<wsrep::mutex>&, wsrep::client_state::state): Assertion `wsrep::this_thread::get_id() == owning_thread_id_' failed.
200718 18:05:36 [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: 10.4.13-MariaDB-log
key_buffer_size=1048576
read_buffer_size=4194304
max_used_connections=81
max_threads=102
thread_count=608
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 7105983 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7faba0000c08
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 = 0x7faf58e52c68 thread_stack 0x40000

• • • buffer overflow detected ***: /usr/sbin/mysqld terminated