Resource Exhaustion Affecting podman-gvproxy package, versions *

Note: Versions mentioned in the description apply only to the upstream podman-gvproxy package and not the podman-gvproxy package as distributed by Centos. See How to fix? for Centos:8 relevant fixed versions and status.

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.

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