Bug 2533833

Summary:	CVE-2026-53495 doctl: containerd: Denial of Service via CRI ExecSync goroutine leak [fedora-all]
Product:	[Fedora] Fedora	Reporter:	Matteo Signorini <msignori>
Component:	doctl	Assignee:	Mikel Olasagasti Uranga <mikel>
Status:	CLOSED ERRATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	go-sig, mikel
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	{"flaws": ["80b4650f-94e7-4a64-87fe-84ae632f1379"]}
Fixed In Version:	doctl-1.169.0-1.fc44 doctl-1.169.0-1.fc45	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-09-20 01:20:25 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:	2533230

Description Matteo Signorini 2026-09-15 14:14:26 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. Prior to 1.7.35, 2.0.12, 2.2.8, and 2.3.5, containerd on Linux with the CRI plugin enabled can indefinitely block the drainExecSyncIO goroutine in internal/cri/server/container_execsync.go when CRI ExecSync is used by exec probes or lifecycle hooks that launch long-lived background child processes retaining standard input and output pipes. The input and output drain phase has no default timeout and did not stop when the request context was canceled, so repeated ExecSync invocations can accumulate blocked goroutines and host memory. The resulting resource exhaustion can cause the OOM killer to terminate containerd, leaving the container runtime unavailable until restart. Deployments not using containerd's CRI implementation and containers not running on Linux are not affected. This issue is fixed in versions 1.7.35, 2.0.12, 2.2.8, and 2.3.5.

Comment 1 Fedora Update System 2026-09-18 22:29:51 UTC

FEDORA-2026-a205d8bdfd (doctl-1.169.0-1.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-a205d8bdfd

Comment 2 Fedora Update System 2026-09-18 22:30:13 UTC

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

Comment 3 Fedora Update System 2026-09-19 01:41:12 UTC

FEDORA-2026-a205d8bdfd has been pushed to the Fedora 45 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-a205d8bdfd`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-a205d8bdfd

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

Comment 4 Fedora Update System 2026-09-19 02:20:07 UTC

FEDORA-2026-ad8394dc92 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-ad8394dc92`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-ad8394dc92

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

Comment 5 Fedora Update System 2026-09-20 01:20:25 UTC

FEDORA-2026-ad8394dc92 (doctl-1.169.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-09-22 00:19:09 UTC

FEDORA-2026-a205d8bdfd (doctl-1.169.0-1.fc45) has been pushed to the Fedora 45 stable repository.
If problem still persists, please make note of it in this bug report.