CVE-2024-3056

Podman: kernel: containers in shared ipc namespace are vulnerable to denial of service attack

State
Published
Severity
7.7 High
Published
Aug 2, 2024
Updated
Oct 29, 2026
Reserved
Mar 28, 2024

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.17.7 HighCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:Hredhat

Weaknesses

  • CWE-400 Uncontrolled Resource Consumption

Affected Products

ProductVersions
podman
  • 5.0.0Affected
Red Hat Enterprise Linux 10Red Hat
    Red Hat Enterprise Linux 7Red Hat
      Red Hat Enterprise Linux 7Red Hat
        Red Hat Enterprise Linux 7Red Hat
          Red Hat Enterprise Linux 8Red Hat
            Red Hat Enterprise Linux 8Red Hat
              Red Hat Enterprise Linux 8Red Hat
                Red Hat Enterprise Linux 8Red Hat
                  Red Hat Enterprise Linux 9Red Hat
                    Red Hat Enterprise Linux 9Red Hat
                      Red Hat OpenShift Container Platform 3.11Red Hat
                        Red Hat OpenShift Container Platform 4Red Hat

                          References

                          Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.