Bug 2496559 - CVE-2026-53492 helm3: containerd: Security bypass via Container Device Interface (CDI) annotation smuggling during checkpoint restoration. [epel-all]
Summary: CVE-2026-53492 helm3: containerd: Security bypass via Container Device Interf...
Keywords:
Status: NEW
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: helm3
Version: epel10
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Mikel Olasagasti Uranga
QA Contact:
URL:
Whiteboard: {"flaws": ["57b7349e-046e-4b0a-b5ee-9...
Depends On:
Blocks: CVE-2026-53492
TreeView+ depends on / blocked
 
Reported: 2026-07-02 14:53 UTC by Rohit Keshri
Modified: 2026-07-02 14:53 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Rohit Keshri 2026-07-02 14:53:04 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.

containerd is an open-source container runtime. In Versions prior to 2.3.2, 2.2.5 and 2.1.9, the CRI implementation improperly trusts Container Device Interface (CDI) annotations found within untrusted checkpoint image metadata during container restoration. When restoring a container from a checkpoint, containerd preserves CDI-related annotations from the checkpoint archive rather than relying solely on the pod's create-time specification. This allows a user with pod creation permissions to bypass standard Kubernetes resource allocation and device plugin enforcement, injecting arbitrary CDI edits (such as device nodes and host mounts) into the restored container. Successful exploitation requires that the node has CDI enabled and contains a matching host CDI specification for the requested device; environments where CDI is disabled or lacking sensitive device specifications are not affected. This issue has been fixed in versions 2.3.2, 2.2.5 and 2.1.9.


Note You need to log in before you can comment on or make changes to this bug.