Bug 2496562

Summary:	CVE-2026-53492 doctl: containerd: Security bypass via Container Device Interface (CDI) annotation smuggling during checkpoint restoration. [fedora-all]
Product:	[Fedora] Fedora	Reporter:	Rohit Keshri <rkeshri>
Component:	doctl	Assignee:	Mikel Olasagasti Uranga <mikel>
Status:	CLOSED ERRATA	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	rawhide	CC:	go-sig, mikel
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	{"flaws": ["57b7349e-046e-4b0a-b5ee-9960edd2eb00"]}
Fixed In Version:	doctl-1.164.0-1.fc44 doctl-1.164.0-1.fc43	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-08-05 00:55:38 UTC	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:	2496130

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

Comment 1 Fedora Update System 2026-07-27 08:20:40 UTC

FEDORA-2026-7ca1b24b3c (doctl-1.164.0-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-7ca1b24b3c

Comment 2 Fedora Update System 2026-07-27 08:21:09 UTC

FEDORA-2026-a36bdff8d7 (doctl-1.164.0-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-a36bdff8d7

Comment 3 Fedora Update System 2026-07-28 01:35:06 UTC

FEDORA-2026-7ca1b24b3c has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-7ca1b24b3c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-7ca1b24b3c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2026-07-28 01:56:40 UTC

FEDORA-2026-a36bdff8d7 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-a36bdff8d7`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-a36bdff8d7

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2026-08-05 00:55:38 UTC

FEDORA-2026-7ca1b24b3c (doctl-1.164.0-1.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2026-08-05 01:10:11 UTC

FEDORA-2026-a36bdff8d7 (doctl-1.164.0-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.