Answer in brief
CVE-2026-68234 records a Unknown severity vulnerability in drm/amdgpu: fix bo->pin leaking in amdgpu_bo_create_reserved. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <51eeef1949c11d3dcb5f422a5d9b3f09ebe8a1bc || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2f390b4c83011452753fd84972f657d2b00a952b || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ba7b6444097a73ccd3d3ac9e2be4ebb73d226460 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9743f60013273987abf415dc47474683d22aaee9 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a2f895f3c852063258d62e9f74b081de07ca95df || >=0 <6.6.148 || >=0 <6.12.101 || >=0 <6.18.42 || >=0 <7.1.6 | 51eeef1949c11d3dcb5f422a5d9b3f09ebe8a1bc, 2f390b4c83011452753fd84972f657d2b00a952b, ba7b6444097a73ccd3d3ac9e2be4ebb73d226460, 9743f60013273987abf415dc47474683d22aaee9, a2f895f3c852063258d62e9f74b081de07ca95df, 6.6.148, 6.12.101, 6.18.42, 7.1.6 |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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)
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68234 records a Unknown severity vulnerability in drm/amdgpu: fix bo->pin leaking in amdgpu_bo_create_reserved. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <51eeef1949c11d3dcb5f422a5d9b3f09ebe8a1bc || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2f390b4c83011452753fd84972f657d2b00a952b || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ba7b6444097a73ccd3d3ac9e2be4ebb73d226460 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9743f60013273987abf415dc47474683d22aaee9 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a2f895f3c852063258d62e9f74b081de07ca95df || >=0 <6.6.148 || >=0 <6.12.101 || >=0 <6.18.42 || >=0 <7.1.6 | 51eeef1949c11d3dcb5f422a5d9b3f09ebe8a1bc, 2f390b4c83011452753fd84972f657d2b00a952b, ba7b6444097a73ccd3d3ac9e2be4ebb73d226460, 9743f60013273987abf415dc47474683d22aaee9, a2f895f3c852063258d62e9f74b081de07ca95df, 6.6.148, 6.12.101, 6.18.42, 7.1.6 |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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)
Quoted source text, attributed separately from HOL analysis.