Bug 2533230 (CVE-2026-53495) - CVE-2026-53495 github.com/containerd/containerd: containerd: Denial of Service via CRI ExecSync goroutine leak
Summary: CVE-2026-53495 github.com/containerd/containerd: containerd: Denial of Servic...
Keywords:
Status: NEW
Alias: CVE-2026-53495
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2533720 2533721 2533812 2533814 2533815 2533816 2533818 2533819 2533820 2533821 2533822 2533823 2533824 2533825 2533826 2533827 2533828 2533829 2533831 2533834 2533835 2533833
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-14 17:33 UTC by OSIDB Bzimport
Modified: 2026-09-15 14:15 UTC (History)
126 users (show)

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


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-14 17:33:57 UTC
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.


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