Bug 2544449

Summary: CVE-2026-15801 cri-o1.34: cri-o: Insufficient validation during container checkpoint restore [fedora-44]
Product: [Fedora] Fedora Reporter: Yadnyawalk Tale <ytale>
Component: cri-o1.34Assignee: Brad Smith <bradley.g.smith>
Status: NEW --- QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 44CC: bradley.g.smith, go-sig
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: {"flaws": ["405404c9-a0fc-4c08-aeb7-02080d66aa20"]}
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2500823    

Description Yadnyawalk Tale 2026-10-01 06:47:15 UTC 
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

A flaw was discovered in CRI-O's checkpoint and restore capability. If a container is restored from a checkpoint archive, CRI-O does not adequately validate the restore metadata. A sufficiently privileged user could therefore cause unintended host filesystem activity during the restore process. This behavior is only reachable when checkpoint and restore has been explicitly enabled; it is not active in the default CRI-O/OpenShift configuration. Exploitation also depends on the attacker being able to initiate a restore operation using checkpoint data that they control or supply.