A flaw was found in CRI-O in the way it set kernel options for a pod. This issue allows 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, where the malicious pod was deployed.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alpine Linux | — | Upgrade cri-o | Aug 8, 2025 | Mar 16, 2022 |
| Oracle_linux | — | Upgrade cri-o | Mar 18, 2022 | Mar 16, 2022 |
| Redhat Openshift | — | Upgrade cri-o | Mar 17, 2022 | Mar 15, 2022 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub