In the Linux kernel, the following vulnerability has been resolved: drm/gem: fix race between change_handle and handle_delete drm_gem_change_handle_ioctl leaves the old handle live in the IDR during the window between spin_unlock(table_lock) and the final spin_lock(table_lock). A concurrent drm_gem_handle_delete on the old handle succeeds in this window, decrements handle_count to 0, and frees the GEM object while the new handle's IDR entry still references it. NULL the old handle's IDR entry before dropping table_lock so that any concurrent GEM_CLOSE on the old handle sees NULL and returns -EINVAL. Restore the old entry on the prime-bookkeeping error path.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://git.kernel.org/stable/c/0dfa42cfe4dbe114533480503934f43e33c1e83d Patch
- https://git.kernel.org/stable/c/7164d78559b0ff29931a366a840a9e5dd53d4b7c Patch
- https://git.kernel.org/stable/c/cde2c9257cbe8463b9dcf7b1075177b72b5fd938 Patch
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 5
- Cpes+4 CPE criteria (now 4)NVD modified 2026-10-26 20:16
- StatusPublished → AnalyzedNVD modified 2026-10-26 20:16
- StatusAwaiting Analysis → PublishedNVD modified 2026-10-19 20:17
- CwesCWE-362NVD modified 2026-10-19 21:17
- First seenCVSS 8.8NVD modified 2026-10-16 16:18
Affected (CPE criteria) 4
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:7.1:rc5:*:*:*:*:*:*