CVE-2026-68234None▾ SunlitIn 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 param…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.
Exploit-prediction probability, daily snapshots since Nov 6.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.2%
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)
Linux >= 53766e5adac75872e9d413cdbfd0e47ae40701f9 < 7aea619d9f186dcf0f1289879e9edb69d2b56639Linux >= 53766e5adac75872e9d413cdbfd0e47ae40701f9 < b572d0814c1366701ca704286589fab025802566Linux >= 53766e5adac75872e9d413cdbfd0e47ae40701f9 < e06e0885725a16304b7723aeb478a78cca9dc96aLinux >= 53766e5adac75872e9d413cdbfd0e47ae40701f9 < 51eeef1949c11d3dcb5f422a5d9b3f09ebe8a1bcLinux >= 53766e5adac75872e9d413cdbfd0e47ae40701f9 < 2f390b4c83011452753fd84972f657d2b00a952bLinux >= 53766e5adac75872e9d413cdbfd0e47ae40701f9 < ba7b6444097a73ccd3d3ac9e2be4ebb73d226460Linux >= 53766e5adac75872e9d413cdbfd0e47ae40701f9 < 9743f60013273987abf415dc47474683d22aaee9Linux >= 53766e5adac75872e9d413cdbfd0e47ae40701f9 < a2f895f3c852063258d62e9f74b081de07ca95dfLinux 4.14Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99284Nonenet: skbuff: propagate shared-frag marker in skb_zerocopy()
CVE-2026-99283Nonenetfilter: conntrack: tcp: use UNACK timeout for non-closing RST packets
CVE-2026-99272Nonesmb: client: validate the data area in SMB2_read()
CVE-2026-99271NoneALSA: line6: Clear prev_fbuf on capture buffer release
CVE-2026-99273Noneksmbd: reserve space for the UTF-16 terminator in stream info
CVE-2026-99275Nonesmb: client: reject short SESSION_SETUP responses