# CVE-2025-68252: misc: fastrpc: Fix dma_buf object leak in fastrpc_map_lookup

> A local attacker can trigger a memory leak in the Linux kernel's fastrpc driver, potentially leading to denial of service.

- **Severity:** Not scored
- **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:** 16 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-68252, GHSA-2c92-jwmp-9jr9, UBUNTU-CVE-2025-68252

## What is CVE-2025-68252?

CVE-2025-68252 is a memory corruption vulnerability in Linux, published on 16 Dec 2025. 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:

misc: fastrpc: Fix dma_buf object leak in fastrpc_map_lookup

In fastrpc_map_lookup, dma_buf_get is called to obtain a reference to
the dma_buf for comparison purposes. However, this reference is never
released when the function returns, leading to a dma_buf memory leak.

Fix this by adding dma_buf_put before returning from the function,
ensuring that the temporarily acquired reference is properly released
regardless of whether a matching map is found.

Rule: add

## Which versions are affected by CVE-2025-68252?


## How do I fix CVE-2025-68252?

Apply the vendor's patch.

## Is CVE-2025-68252 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68252 and fix it if it is affected.

What it is: CVE-2025-68252 is a memory corruption vulnerability in Linux, published on 16 Dec 2025. 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-2025-68252 in the wild and no public exploit code.

Affected product: Linux. 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-2025-68252/ (Markdown: https://insights.sbomify.com/CVE-2025-68252/index.md)
```

## Sources

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

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