CVE-2026-46215 drm: Set old handle to NULL before prime swap in change_handle

High 7.8 Published Updated

A race condition in the Linux kernel DRM subsystem allows a use-after-free, potentially enabling local attackers to execute code or escalate privileges.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-46215?

CVE-2026-46215 is a high-severity use after free vulnerability in Linux kernel, published on 28 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

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

Weakness: CWE-416

Which versions are affected by CVE-2026-46215?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2026-46215?

Apply the vendor's patch.

Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.

Is CVE-2026-46215 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46215 exists.

Public exploit code: 3 proofs of concept on GitHub.

All Linux kernel vulnerabilities

Sources

Also known as BELL-CVE-2026-46215, DEBIAN-CVE-2026-46215, GHSA-gm2j-59pp-6cxj, UBUNTU-CVE-2026-46215.

Is CVE-2026-46215 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free