InnoDB: Assertion failure in file ./storage/innobase/buf/buf0lru.cc line 281

MariaDB 10.11.8 suddenly crash with following crash log:

260508 12:16:28 [ERROR] mysqld got signal 11 ;
Sorry, we probably made a mistake, and this is a bug.

Your assistance in bug reporting will enable us to fix this for the next release.
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.11.8-MariaDB-ubu2204-log source revision: 3a069644682e336e445039e48baae9693f9a08ee
key_buffer_size=536870912
read_buffer_size=4194304
max_used_connections=1157
max_threads=3002
thread_count=826
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 62085430 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fd458189c78
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 = 0x7fd941221c78 thread_stack 0x49000
2026-05-08 12:16:30 0x7fd89e238640 InnoDB: Assertion failure in file ./storage/innobase/buf/buf0lru.cc line 281
InnoDB: Failing assertion: !block->page.in_file()
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mariadbd startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
Fatal signal 6 while backtracing