# CVE-2026-68234: drm/amdgpu: fix bo->pin leaking in amdgpu_bo_create_reserved

> A resource leak in the AMDGPU driver can cause memory exhaustion and denial of service when firmware buffers are repeatedly reloaded.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** BELL-CVE-2026-68234, DEBIAN-CVE-2026-68234, GHSA-4jjq-9h58-5wmm, UBUNTU-CVE-2026-68234

## What is CVE-2026-68234?

CVE-2026-68234 is a denial of service vulnerability in Linux, published on 10 Aug 2026. 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:

drm/amdgpu: fix bo->pin leaking in amdgpu_bo_create_reserved

amdgpu_bo_create_reserved() only allocates a new BO when
*bo_ptr (struct amdgpu_bo **bo_ptr as input parameter) is
NULL, it simply skips creation when *bo_ptr is non-NULL.
But it unconditionally reserves, pins, gart allocates
and maps the BO afterwards.

When the same non-NULL BO pointer is passed in again,
for example firmware buffers that live in adev and are
re-loaded on every resume / cp_resume / start
under AMDGPU_FW_LOAD_DIRECT, amdgpu_bo_pin() just increases
pin_count unconditionally, however the matching teardown only unpins
once, so pin_count never drops to zero, so TTM is not able
to move, swap or evict a BO, causing BO leaks.

This commit fixes this issue by only pinning the bo
once at creation, and repeated calls no longer
take additional pin references.

(cherry picked from commit 3ddc0ae76202c447b6aec61e907b852bc94671cf)

## Which versions are affected by CVE-2026-68234?


## How do I fix CVE-2026-68234?

Apply the vendor's patch.

## Is CVE-2026-68234 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68234 and fix it if it is affected.

What it is: CVE-2026-68234 is a denial of service vulnerability in Linux, published on 10 Aug 2026. 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-2026-68234 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-2026-68234/ (Markdown: https://insights.sbomify.com/CVE-2026-68234/index.md)
```

## Sources

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

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