CVE-2023-6476: CRI-O's pods can break out of resource confinement on cgroupv2
Impact What kind of vulnerability is it? Who is impacted? All versions of CRI-O running on cgroupv2 nodes. Unchecked access to an experimental annotation allows a container to be unconfined. Back in 2021, support was added to support an experimental annotation that allows a user to request special resources in cgroupv2.
Published Jan 10, 2024 · Updated Jan 19, 2024
Affected packages
github.com/cri-o/cri-o
- Ecosystem
- Go
- Affected
- = 1.29.0
- Fixed in
- 1.29.1
- Check
go list -m github.com/cri-o/cri-o
github.com/cri-o/cri-o
- Ecosystem
- Go
- Affected
- >= 1.28.0, < 1.28.3
- Fixed in
- 1.28.3
- Check
go list -m github.com/cri-o/cri-o
github.com/cri-o/cri-o
- Ecosystem
- Go
- Affected
- < 1.27.3
- Fixed in
- 1.27.3
- Check
go list -m github.com/cri-o/cri-o
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
_What kind of vulnerability is it? Who is impacted?_ All versions of CRI-O running on cgroupv2 nodes. Unchecked access to an experimental annotation allows a container to be unconfined. Back in 2021, support was added to support an experimental annotation that allows a user to request special resources in cgroupv2. It was supposed to be gated by an experimental annotation: io.kubernetes.cri-o.UnifiedCgroup, which was supposed to be filtered from the list of allowed annotations . However, there is a bug in this code which allows any user to specify this annotation, regardless of whether it's enabled on the node. The consequences of this are a pod can specify any amount of memory/cpu and get it, circumventing the kubernetes scheduler, and potentially be able to DOS a node.
Patches
_Has the problem been patched? What versions should users upgrade to?_ 1.29.1, 1.28.3, 1.27.3
Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_ use cgroupv1
References
_Are there any links users can visit to find out more?_
Credited to Tal-or.
References
- https://github.com/cri-o/cri-o/security/advisories/GHSA-p4rx-7wvg-fwrc
- https://nvd.nist.gov/vuln/detail/CVE-2023-6476
- https://github.com/cri-o/cri-o/pull/4479
- https://github.com/cri-o/cri-o/commit/75effcb1a25851a736e82dba1f7d8cee93ee159e
- https://access.redhat.com/security/cve/CVE-2023-6476
- https://bugzilla.redhat.com/show_bug.cgi?id=2253994
- https://github.com/cri-o/cri-o/blob/main/pkg/config/workloads.go#L103-L107
- https://access.redhat.com/errata/RHSA-2024:0195
- https://access.redhat.com/errata/RHSA-2024:0207
- https://github.com/advisories/GHSA-p4rx-7wvg-fwrc
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2025-4437
CRI-O has Potential High Memory Consumption from File Read
medium5.7No fixAug 20, 2025CVE-2025-0750
CRI-O Path Traversal vulnerability
medium6.6No fixJan 28, 2025CVE-2024-8676
CRI-O: Maliciously structured checkpoint file can gain arbitrary node access
medium7.4Nov 26, 2024CVE-2024-5154
malicious container creates symlink "mtab" on the host External
high8.1Jun 4, 2024CVE-2024-3154
CRI-O vulnerable to an arbitrary systemd property injection
high7.2Apr 30, 2024
