What is CVE-2026-46215?
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
The record classifies CVE-2026-46215 under weakness class CWE-416. Its CVSS v3 base vector states that the flaw requires local access to the host, needs low-privilege credentials, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 153 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 7.8 — HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - EPSS (FIRST)
- 0.1% probability of exploitation in the next 30 days, higher than 5.8% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 6.1/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-05-28, last modified 2026-08-05
Is CVE-2026-46215 being exploited?
Weaponised exploit code for CVE-2026-46215 is publicly available. 4 public proof-of-concept repositories are tracked for this identifier. It currently carries a trending score of 14 in the Threadlinqs vulnerability feed.
- 0xCyberstan/CVE-2026-46215-POC (github)
- bluedragonsecurity/CVE-2026-46215-exploit-linux-7.0-uaf-stable (github)
- bluedragonsecurity/CVE-2026-46215-EXPLOIT (github)
- trickest/cve (trickest)
Affected products and versions
- Linux: Linux
How to fix CVE-2026-46215
The record marks a vendor fix as available for CVE-2026-46215. Patch reference: https://git.kernel.org/stable/c/5e28b7b94408897e41c63477aabc9e1db439bc8c. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.
Threat activity tracking CVE-2026-46215
1 tracked threat in the Threadlinqs corpus references CVE-2026-46215, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Enriched from CVE.org, NVD, FIRST EPSS, public proof-of-concept repositories. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.