containerd CRI ExecSync Goroutine Leak Leading to Node-Level Denial of Service
containerd
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containerd/containerd/v2 Go |
|
|
| github.com/containerd/containerd Go |
containerd
| Product | Affected | Fixed in |
|---|---|---|
| github.com/containerd/containerd/v2 Go |
|
|
| github.com/containerd/containerd Go |
< 1.7.35
|
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.
From the CVE record · GitHub_M
On Linux, containerd's CRI ExecSync can leave I/O-draining goroutines blocked indefinitely when exec probes or lifecycle hooks launch long-lived background child processes that retain standard input and output pipes. Repeated invocations can exhaust host memory and cause the OOM killer to terminate containerd. The input does not specify an attacker access path or authentication requirements; the issue requires the CRI plugin and this ExecSync behavior.
Operators running containerd on Linux with the CRI plugin enabled should check Go package github.com/containerd/containerd versions before 1.7.35 and github.com/containerd/containerd/v2 versions before 2.0.12, 2.2.0 through 2.2.7, or 2.3.0 through 2.3.4.