CVE-2026-68234

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

N/A
Published: August 10, 2026 at 12:00 PM UTC
Updated: August 19, 2026 at 05:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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)

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.14 ≤ v < 5.10.2654.14 ≤ v < 5.15.2164.14 ≤ v < 6.1.1834.14 ≤ v < 6.12.1014.14 ≤ v < 6.18.424.14 ≤ v < 6.6.1484.14 ≤ v < 7.1.64.14 ≤ v < 7.24.1453766e5adac75872e9d413cdbfd0e47ae40701f9
Vendor states this is fixed in 2f390b4c83011452753fd84972f657d2b00a952b (fixed)
Vendor states this is fixed in 51eeef1949c11d3dcb5f422a5d9b3f09ebe8a1bc (fixed)
Vendor states this is fixed in 7aea619d9f186dcf0f1289879e9edb69d2b56639 (fixed)
Vendor states this is fixed in 9743f60013273987abf415dc47474683d22aaee9 (fixed)
Vendor states this is fixed in a2f895f3c852063258d62e9f74b081de07ca95df (fixed)
Vendor states this is fixed in b572d0814c1366701ca704286589fab025802566 (fixed)
Vendor states this is fixed in ba7b6444097a73ccd3d3ac9e2be4ebb73d226460 (fixed)
Vendor states this is fixed in e06e0885725a16304b7723aeb478a78cca9dc96a (fixed)
Vendor states this is fixed in 4.14 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card