---
id: CVE-2024-3056
title: >-
  Podman: kernel: containers in shared ipc namespace are vulnerable to denial of
  service attack
summary: >-
  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. T…
severity: high
cvss: 7.7
cvssVector: 'CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:H'
cvssSource: cna
cwe:
  - CWE-400
vendor: Red Hat
product: podman
affected:
  - podman 5.0.0
  - kernel (all versions)
  - kernel
  - kernel-rt
  - podman
  - 'container-tools:4.0/podman'
  - 'container-tools:rhel8/podman'
  - kernel (all versions)
  - kernel-rt (all versions)
  - kernel (all versions)
  - podman
  - podman
  - podman
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2024-08-03T18:09:31.742310Z'
published: '2024-08-02'
updated: '2026-10-29'
sourceUpdated: '2026-10-29T06:31:41.169Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2024-3056'
references:
  - url: 'https://access.redhat.com/security/cve/CVE-2024-3056'
  - url: 'https://bugzilla.redhat.com/show_bug.cgi?id=2270717'
    label: RHBZ#2270717
tags:
  - cve.org
epss: 0.00545
epssPercentile: 0.4574
ingestedAt: '2026-10-31T04:17:25.421Z'
---

## Overview

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.

## Affected

- `podman 5.0.0`
- `kernel (all versions)`
- `kernel`
- `kernel-rt`
- `podman`
- `container-tools:4.0/podman`
- `container-tools:rhel8/podman`
- `kernel (all versions)`
- `kernel-rt (all versions)`
- `kernel (all versions)`
- `podman`
- `podman`
- `podman`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.

### Workarounds

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.