Skip to content
OpenAdvisories
Medium · 6.5 CVE-2023-6476 EUVD-2024-0390GHSA-p4rx-7wvg-fwrcGO-2024-2458

Cri-o: pods are able to break out of resource confinement on cgroupv2

Published Jan 9, 2024 · Updated Nov 20, 2025 · Assigned by redhat

Description

A flaw was found in CRI-O that involves an experimental annotation leading to a container being unconfined. This may allow a pod to specify and get any amount of memory/cpu, circumventing the kubernetes scheduler and potentially resulting in a denial of service in the node.

Affected products

VendorProductAffectedFixed
Red Hat Red Hat OpenShift Container Platform 4.13 — —
Red Hat Red Hat OpenShift Container Platform 4.14 — —
Red Hat Red Hat OpenShift Container Platform 3.11 — —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
Red Hat OpenShift 4 cri-o 1.26.4-6.1.rhaos4.13.git9eb9cf3.el8 RHSA-2024:0207, RHSA-2024:0195

Azure Linux

ReleasePackageFixed inAdvisory
Azure Linux 2 (CBL-Mariner) cri-o 1.22.3-10 —

Affected packages

EcosystemPackageAffectedFixedRecord
Go github.com/cri-o/cri-o >= 1.29.0, < 1.29.1 1.29.1 GHSA-p4rx-7wvg-fwrc
Go github.com/cri-o/cri-o >= 1.28.0, < 1.28.3 1.28.3 GHSA-p4rx-7wvg-fwrc
Go github.com/cri-o/cri-o < 1.27.3 1.27.3 GHSA-p4rx-7wvg-fwrc
Go github.com/cri-o/cri-o < 1.27.3 · >= 1.28.0, < 1.28.3 · >= 1.29.0, < 1.29.1 1.27.3, 1.28.3, 1.29.1 GO-2024-2458

Advisories 3

References