CVE-2026-68234

CVE CVE-2026-68234EUVD EUVD-2026-55335Published 2026-08-10T12:00:59.000Z

What the advisory describes

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)

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <51eeef1949c11d3dcb5f422a5d9b3f09ebe8a1bc; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a2f895f3c852063258d62e9f74b081de07ca95df; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ba7b6444097a73ccd3d3ac9e2be4ebb73d226460; patch: 6.18.42; patch: 6.12.101; 0 <6.12.101; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9743f60013273987abf415dc47474683d22aaee9; 0 <6.6.148; patch: 6.6.148; 0 <6.18.42; patch: 7.1.6; 0 <7.1.6; patch: 7.2-rc4; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2f390b4c83011452753fd84972f657d2b00a952b

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.