Slave crash with index corruption during UPDATE

A slave crashed on trivial, single-line UPDATE from master. Queries like this one were executed successfully thousands of times before.

RHEL runs in a VMWare VM with storage over FC/SAN, so no immediate hardware failure is suspected. The VM runs with 8 GB RAM and usually has less than 100 concurrent connections; no OOM actions logged by the OS. While there are multiple databases active, no other MariaDB or OS errors were logged before the crash (e.g., like max open files limit
exhausted et al). The VM is restarted on weekly basis.

The immediate error messages were:

InnoDB: Page old data size 270 new data size 402, page old max ins size 15980 new max ins size 15848

Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.12/storage/innobase/btr/btr0cur.cc line 4879

Failing assertion: page_zip || optim_err != DB_UNDERFLOW

System log messages are attached.

After this point MariaDB as unable to restart at all with, which required a backup/restore from master.

I could not find anything similar in Jira, hence opening this for possible consideration.