https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 10:22:50 +0000 https://vulnerability.circl.lu/vuln/cve-2026-68234 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/amdgpu: fix bo-&gt;pin leaking in amdgpu_bo_create_reserved</p> <p>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.</p> <p>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.</p> <p>This commit fixes this issue by only pinning the bo once at creation, and repeated calls no longer take additional pin references.</p> <p>(cherry picked from commit 3ddc0ae76202c447b6aec61e907b852bc94671cf)</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/amdgpu: fix bo-&gt;pin leaking in amdgpu_bo_create_reserved</p> <p>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.</p> <p>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.</p> <p>This commit fixes this issue by only pinning the bo once at creation, and repeated calls no longer take additional pin references.</p> <p>(cherry picked from commit 3ddc0ae76202c447b6aec61e907b852bc94671cf)</p> https://vulnerability.circl.lu/vuln/cve-2026-68234