CVE-2026-46215
Received Received - Intake
Race Condition in Linux Kernel DRM Handle Management

Publication date: 2026-05-28

Last updated on: 2026-05-28

Assigner: kernel.org

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
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-28
Last Modified
2026-05-28
Generated
2026-05-28
AI Q&A
2026-05-28
EPSS Evaluated
N/A
NVD
CVE-2026-46215
EUVD
EUVD-2026-32842
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability exists in the Linux kernel's Direct Rendering Manager (drm) subsystem, specifically in the change_handle function.

There was a potential race condition where the ioctl briefly had a single object with two idr entries. During this time, a concurrent gem_close operation could delete the object and remove one of the handles while leaving the other handle dangling.

This dangling handle could then be dereferenced, leading to a use-after-free condition, which is a type of memory corruption vulnerability.

The fix involved setting the old handle to NULL before swapping it in change_handle, ensuring that the object references are properly managed and preventing the race condition.


How can this vulnerability impact me? :

This vulnerability can lead to a use-after-free scenario in the Linux kernel's drm subsystem.

Use-after-free vulnerabilities can cause system instability, crashes, or potentially allow an attacker to execute arbitrary code with kernel privileges.

Therefore, if exploited, this vulnerability could compromise the security and stability of a system running the affected Linux kernel.


What immediate steps should I take to mitigate this vulnerability?

The vulnerability is resolved by updating the Linux kernel to a version that includes the fix for the race condition in the drm subsystem, specifically the change_handle function.

Immediate mitigation involves applying the kernel patch that sets the old handle to NULL before prime swap in change_handle, preventing use-after-free conditions.

Therefore, the recommended step is to update your Linux kernel to the fixed version released on or after 2026-05-28.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart