VulnerabilityPublished 10 Aug 2026Updated 6 Nov 2026

CVE-2026-68234: Linux kernel · drm/amdgpu: fix bo->pin leaking in amdgpu_bo_create_reserved

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in e06e0885725a16304b7723aeb478a78cca9dc96a : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:04 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch

Available – fixed in e06e0885725a16304b7723aeb478a78cca9dc96a, ba7b6444097a73ccd3d3ac9e2be4ebb73d226460, b572d0814c1366701ca704286589fab025802566 +5

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 53766e5adac75872e9d413cdbfd0e47ae40701f9, < e06e0885725a16304b7723aeb478a78cca9dc96a	Fixed in e06e0885725a16304b7723aeb478a78cca9dc96a
LinuxLinux	Affected ≥ 53766e5adac75872e9d413cdbfd0e47ae40701f9, < ba7b6444097a73ccd3d3ac9e2be4ebb73d226460	Fixed in ba7b6444097a73ccd3d3ac9e2be4ebb73d226460
LinuxLinux	Affected ≥ 53766e5adac75872e9d413cdbfd0e47ae40701f9, < b572d0814c1366701ca704286589fab025802566	Fixed in b572d0814c1366701ca704286589fab025802566
LinuxLinux	Affected ≥ 53766e5adac75872e9d413cdbfd0e47ae40701f9, < a2f895f3c852063258d62e9f74b081de07ca95df	Fixed in a2f895f3c852063258d62e9f74b081de07ca95df
LinuxLinux	Affected ≥ 53766e5adac75872e9d413cdbfd0e47ae40701f9, < 9743f60013273987abf415dc47474683d22aaee9	Fixed in 9743f60013273987abf415dc47474683d22aaee9
LinuxLinux	Affected ≥ 53766e5adac75872e9d413cdbfd0e47ae40701f9, < 51eeef1949c11d3dcb5f422a5d9b3f09ebe8a1bc	Fixed in 51eeef1949c11d3dcb5f422a5d9b3f09ebe8a1bc

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)

References

Community reviews

Loading reviews…