Amazon Linux 2 (EOS) Security Advisory: ALAS2DOCKER-2026-144
Advisory Released Date: 2026-10-12
Advisory Updated Date: 2026-10-12
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. (CVE-2026-53495)
Affected Packages:
containerd
Note:
This advisory is applicable to Amazon Linux 2 - Docker Extra. Visit this page to learn more about Amazon Linux 2 (AL2) Extras and this FAQ section for the difference between AL2 Core and AL2 Extras advisories.
Issue Correction:
Run yum update containerd or yum update --advisory ALAS2DOCKER-2026-144 to update your system.
aarch64:
containerd-2.3.5-1.amzn2.0.1.aarch64
containerd-stress-2.3.5-1.amzn2.0.1.aarch64
containerd-debuginfo-2.3.5-1.amzn2.0.1.aarch64
src:
containerd-2.3.5-1.amzn2.0.1.src
x86_64:
containerd-2.3.5-1.amzn2.0.1.x86_64
containerd-stress-2.3.5-1.amzn2.0.1.x86_64
containerd-debuginfo-2.3.5-1.amzn2.0.1.x86_64