Podman: kernel: containers in shared ipc namespace are vulnerable to denial of service attack
cve-program · CVE-2024-3056 · Published
No access to your tenant or devices. Every item links to its source. What this means
Historical advisory recorded 5 Nov 2026 13:36:20 UTC. Read the latest advisory.
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.
Read the publisher's advisorySee how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.
cve-program · CVE-2024-3056 · Published
cve-program · CVE-2024-3056 · Published
cve-program · CVE-2024-3056 · Published
This historical link shows only this version and versions saved before it. Browse all advisory history.