This came up while I was reviewing
MDEV-29081. It is possible that also older versions than 10.6 are affected by this, but I did not check it.
If Galera invokes ha_abort_transaction() (from wsrep_abort_thd() or wsrep_handle_mdl_conflict()), it will set a flag to have an InnoDB transaction in another thread to be aborted and rolled back.
If no InnoDB conflicts occur, lock_wait() will not be executed and the chosen victim may neglect the request for a long time.
I see that ha_innobase::write_row(), ha_innobase::update_row(), ha_innobase::delete_row() are already doing something extra if trx_t::is_wsrep() holds. I think that those functions need to check the Galera asynchronous kill status.