High [CVE-2024-8676] Cri-o: checkpoint restore can be triggered from different namespaces
This high-severity Red Hat Linux advisory covers CVE-2024-8676 affecting Red Hat OpenShift Container Platform 4.15, Red Hat OpenShift Container Platform 4.16, Red Hat OpenShift Container Platform 4.17.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
A vulnerability was found in CRI-O, where it can be requested to take a checkpoint archive of a container and later be asked to restore it. When it does that restoration, it attempts to restore the mounts from the restore archive instead of the pod request.
As a result, the validations run on the pod spec, verifying that the pod has access to the mounts it specifies are not applicable to a restored container. This flaw allows a malicious user to trick CRI-O into restoring a pod that doesn't have access to host mounts.
The user needs access to the kubelet or cri-o socket to call the restore endpoint and trigger the restore. Red Hat severity: Moderate — CVSS 7.4 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N).
Weakness: CWE-285. Affected Red Hat products: Red Hat OpenShift Container Platform 4.15; Red Hat OpenShift Container Platform 4.16; Red Hat OpenShift Container Platform 4.17; Red Hat OpenShift Container Platform 4.18; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9; Red Hat OpenShift Container Platform 3.11; Red Hat OpenShift Container Platform 4.
Red Hat fixing advisory: RHSA-2025:0648, RHBA-2024:10826, RHSA-2025:9765, RHSA-2025:3297, RHSA-2025:1908, RHSA-2025:4211.
Affected products named by the advisory: Red Hat package: conmon.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
- cri-o-0:1.28.11-7.rhaos4.15.gitc4c0556.el8
- cri-o-0:1.29.11-3.rhaos4.16.git16d9bd6.el8
- rhcos-416.94.202506251808-0
- rhcos-417.94.202503241418-0
- cri-o-0:1.31.5-5.rhaos4.18.git6dfa0a6.el8
- rhcos-418.94.202504231329-0
- RHSA-2025:0648
- RHBA-2024:10826
- RHSA-2025:9765
- RHSA-2025:3297
- RHSA-2025:1908
- RHSA-2025:4211
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Mitigation checklist
- Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.