Node interruption via misplaced container cgroups
Published May 21, 2025 · Updated May 21, 2025
Incorrect cgroup placement in containerd 2.0.1 through 2.0.4 allows attackers to interrupt a Kubernetes node via usernamespaced pods. CRI places each usernamespaced container's systemd cgroup outside its pod's kubepods slice, so Kubernetes resource limits assigned to that hierarchy do not govern the container. Exploitation requires Kubernetes user namespaces and permission to create a usernamespaced pod; ungoverned resource use can exhaust the host and interrupt the node.
Summary
What happened
Incorrect cgroup placement in containerd 2.0.1 through 2.0.4 allows attackers to interrupt a Kubernetes node via usernamespaced pods. CRI places each usernamespaced container's systemd cgroup outside its pod's kubepods slice, so Kubernetes resource limits assigned to that hierarchy do not govern the container. Exploitation requires Kubernetes user namespaces and permission to create a usernamespaced pod; ungoverned resource use can exhaust the host and interrupt the node.
The record
- CVE
- CVE-2025-47291
- Published
- May 21, 2025
- Updated
- May 21, 2025
- Vendor
- containerd
- Product
- containerd
- Classifications
- CWE-266, T1496
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- May 21, 2025CVE publishedPublication date reported by the CVE source.
- May 21, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 2.0.1, < 2.0.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo