Linux
drm: Set old handle to NULL before prime swap in change_handle
In the Linux kernel, the following vulnerability has been resolved: drm: Set old handle to NULL before prime swap in change_handle There was a potential race condition in change_handle. The ioctl briefly had a single object with two idr entries; a concurrent gem_close could delete the object and remove one of the handles while leaving the other one dangling, which could subsequently be dereferenced for a use-after-free. To fix this, do the same dance that gem_close itself does. (f6cd7daecff5 drm: Release driver references to handle before making it available again) First idr_replace the old handle to NULL. Later, if the prime operations are successful, actually close it. create_tail required a similar dance to avoid a similar problem. (bd46cece51a3 drm/gem: Fix race in drm_gem_handle_create_tail()) It idr_allocs the new handle with NULL, then swaps in the correct object later to avoid races. We don't need to do that here, since the only operations that could race are drm_prime, and change_handle holds the prime lock for the entire duration. v2: cleanups of error paths
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 53096728b8910c6916ecc6c46a5abc5c678b58d9, < 672464dd53231509c9c771110798c56d4660e19e
- >= 53096728b8910c6916ecc6c46a5abc5c678b58d9, < 61bd96d3e5472c253f9c1ab77608f0c8aaa9d025
- >= 53096728b8910c6916ecc6c46a5abc5c678b58d9, < 5e28b7b94408897e41c63477aabc9e1db439bc8c
Fixed in 672464dd53231509c9c771110798c56d4660e19e, 61bd96d3e5472c253f9c1ab77608f0c8aaa9d025, 5e28b7b94408897e41c63477aabc9e1db439bc8c
- 6.18
Fixed in 0, 6.18.32, 7.0.9, 7.1
Mitigation
Upgrade Linux to 672464dd53231509c9c771110798c56d4660e19e or 61bd96d3e5472c253f9c1ab77608f0c8aaa9d025 or 5e28b7b94408897e41c63477aabc9e1db439bc8c or later.
Upgrade Linux to 0 or 6.18.32 or 7.0.9 or 7.1 or later.
Timeline
Days relative to CVE publicationFirst public PoC 21 days after publication; not in CISA KEV. First PoC: 0xCyberstan/CVE-2026-46215-POC (created 18 Jun 2026, found by us: backfilled).
PoC repositories
Found on GitHub.3 PoCs · 1 pending · 1 informational
PoCs 3
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| 0xCyberstan/CVE-2026-46215-POC | 18 Jun 2026 +21 d | 11 | PoC |
| bluedragonsecurity/CVE-2026-46215-EXPLOIT | 11 Jul 2026 +44 d | 3 | PoC |
| bluedragonsecurity/CVE-2026-46215-exploit-linux-7.0-uaf-stable | 19 Jul 2026 +52 d | 5 | PoC |
Pending 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| bluedragonsecurity/sheaf_uaf | 28 Jun 2026 +31 d | 3 | Pending · repository exceeds size limit via PoC Index |
Informational 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| bluedragonsecurity/exploits | 13 May 2026 −15 d | 3 | Informational · list |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.