MySQL 8.0.38 does not start (Segmentation Fault) Print

After upgrading to MySQL 8.0.38, mysqld fails to start, and /var/log/mysqld.log shows the following:

2024-07-01T13:54:18.513415Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.38) starting as process 6358
2024-07-01T13:54:18.531309Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-07-01T13:54:21.164353Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2024-07-01T13:54:21Z UTC - mysqld got signal 11 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID[sha1]=539914406f129270c6bd39a48640d0f1eeecc1af
Thread pointer: 0x0
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 = 0 thread_stack 0x100000

The error is due to a bug with MySQL 8.0.38 and cannot be resolved by continuing to run MySQL 8.0.38. You can downgrade on CentOS7 / AlmaLinux / Rocky Linux / CloudLinux systems by doing the following:

yum downgrade mysql-community-*

cPanel, by default, is configured to update system packages automatically daily. Locking the version until a fix is released would also be advisable. You can do so by doing the following:

Install Version Lock Package

CentOS 7 / CloudLinux 7:

yum install yum-versionlock

AlmaLinux 8, Rocky Linux, CloudLinux 8

dnf install python3-dnf-plugin-versionlock

Version Lock MySQL

yum versionlock mysql-community-server

Upon release of a fixed version, we recommend that you remove the version lock so that you continue to receive updates for the MySQL server.