CVE-2026-68234: drm/amdgpu: fix bo->pin leaking in amdgpu_bo_create_reserved
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: fix bo->pin leaking in amdgpubocreatereserved
amdgpubocreatereserved() only allocates a new BO when boptr (struct amdgpubo boptr as input parameter) is NULL, it simply skips creation when boptr 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 / cpresume / start under AMDGPUFWLOADDIRECT, amdgpubopin() just increases pincount unconditionally, however the matching teardown only unpins once, so pincount 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 Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-68234?
CVE-2026-68234 has a risk rating of 22, indicating a significant vulnerability that should be addressed promptly.
How do I fix CVE-2026-68234?
To fix CVE-2026-68234, update your Linux kernel to the latest version where this vulnerability has been patched.
What systems are affected by CVE-2026-68234?
CVE-2026-68234 affects systems running the Linux kernel with the amdgpu driver.
What are the potential impacts of CVE-2026-68234?
The potential impacts of CVE-2026-68234 include memory leaks and performance degradation due to improperly handled buffer objects.
Is CVE-2026-68234 a local or remote vulnerability?
CVE-2026-68234 is considered a local vulnerability as it requires access to the system running the affected Linux kernel.