# CVE-2024-56712: udmabuf: fix memory leak on last export_udmabuf() error path

> A memory leak in the Linux kernel udmabuf driver allows local attackers to exhaust system memory, potentially causing denial of service.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Dec 2024
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-54768, AZL-54896, BELL-CVE-2024-56712, DEBIAN-CVE-2024-56712, GHSA-5546-cr76-j66r, ROOT-OS-DEBIAN-11-CVE-2024-56712, ROOT-OS-DEBIAN-12-CVE-2024-56712, ROOT-OS-UBUNTU-2204-CVE-2024-56712, ROOT-OS-UBUNTU-2404-CVE-2024-56712, UBUNTU-CVE-2024-56712

## What is CVE-2024-56712?

CVE-2024-56712 is a low-severity memory corruption vulnerability in Linux kernel, published on 29 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

udmabuf: fix memory leak on last export_udmabuf() error path

In export_udmabuf(), if dma_buf_fd() fails because the FD table is full, a
dma_buf owning the udmabuf has already been created; but the error handling
in udmabuf_create() will tear down the udmabuf without doing anything about
the containing dma_buf.

This leaves a dma_buf in memory that contains a dangling pointer; though
that doesn't seem to lead to anything bad except a memory leak.

Fix it by moving the dma_buf_fd() call out of export_udmabuf() so that we
can give it different error handling.

Note that the shape of this code changed a lot in commit 5e72b2b41a21
("udmabuf: convert udmabuf driver to use folios"); but the memory leak
seems to have existed since the introduction of udmabuf.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

## Which versions are affected by CVE-2024-56712?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-56712?

Apply the vendor's patch.

## Is CVE-2024-56712 being exploited?

There is no known exploitation of CVE-2024-56712 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-56712 and fix it if it is affected.

What it is: CVE-2024-56712 is a low-severity memory corruption vulnerability in Linux kernel, published on 29 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-56712 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-56712/ (Markdown: https://insights.sbomify.com/CVE-2024-56712/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-56712
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-56712
- OSV: https://osv.dev/vulnerability/CVE-2024-56712

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-56712/
Summaries are generated and may contain mistakes; the official description above is the record.