CVE-2024-3056: Podman vulnerable to memory-based denial of service
A flaw was found in Podman. This issue may allow an attacker to create a specially crafted container that, when configured to share the same IPC with at least one other container, can create a large number of IPC resources in /dev/shm. The malicious container will continue to exhaust resources until it is out-of-memory (OOM) killed.
Published Aug 2, 2024 · Updated Dec 27, 2024
Affected packages
github.com/containers/podman/v5
- Ecosystem
- Go
- Affected
- <= 5.2.0
- Fixed in
- No patched version yet
- Check
go list -m github.com/containers/podman/v5
github.com/containers/podman
- Ecosystem
- Go
- Affected
- <= 5.2.0
- Fixed in
- No patched version yet
- Check
go list -m github.com/containers/podman
github.com/containers/podman/v2
- Ecosystem
- Go
- Affected
- <= 5.2.0
- Fixed in
- No patched version yet
- Check
go list -m github.com/containers/podman/v2
github.com/containers/podman/v3
- Ecosystem
- Go
- Affected
- <= 5.2.0
- Fixed in
- No patched version yet
- Check
go list -m github.com/containers/podman/v3
github.com/containers/podman/v4
- Ecosystem
- Go
- Affected
- <= 5.2.0
- Fixed in
- No patched version yet
- Check
go list -m github.com/containers/podman/v4
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
A flaw was found in Podman. This issue may allow an attacker to create a specially crafted container that, when configured to share the same IPC with at least one other container, can create a large number of IPC resources in /dev/shm. The malicious container will continue to exhaust resources until it is out-of-memory (OOM) killed. While the malicious container's cgroup will be removed, the IPC resources it created are not. Those resources are tied to the IPC namespace that will not be removed until all containers using it are stopped, and one non-malicious container is holding the namespace open. The malicious container is restarted, either automatically or by attacker control, repeating the process and increasing the amount of memory consumed. With a container configured to restart always, such as podman run --restart=always, this can result in a memory-based denial of service of the system.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-94603
Podman: The `podman run` command can be instructed to disable almost all sandboxing by image annotation
critical10.0Oct 15, 2026CVE-2026-19730
podman quadlet install --replace does not fully replace the old file
medium4.2Sep 24, 2026CVE-2026-57231
Podman: Malformed Image can trick podman run into leaking host environment variables into the container
high7.5No fixSep 24, 2026CVE-2026-55686
Podman: WORKDIR symlink traversal vulnerability
medium5.3No fixJun 18, 2026CVE-2026-33414
PowerShell Command Injection in Podman HyperV Machine
medium7.8No fixApr 14, 2026CVE-2025-4953
Podman Creates Temporary File with Insecure Permissions
high7.4No fixSep 16, 2025
