A flaw was found in CRI-O in the way it set kernel options for a pod, allowing anyone with rights to deploy a pod on a Kubernetes cluster that uses the CRI-O runtime to achieve a container escape and arbitrary code execution as root on the cluster node. The issue is related to the lack of proper validation of kernel parameters, which can be exploited by an attacker to bypass safeguards and set arbitrary kernel parameters on the host. This can lead to container escape and arbitrary code execution as root on any node in the cluster.