{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-63885","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2026-07-19T07:54:57.018Z","datePublished":"2026-07-19T14:54:58.590Z","dateUpdated":"2026-08-05T12:36:54.290Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-08-05T12:36:54.290Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/gem: fix race between change_handle and handle_delete\n\ndrm_gem_change_handle_ioctl leaves the old handle live in the IDR\nduring the window between spin_unlock(table_lock) and the final\nspin_lock(table_lock). A concurrent drm_gem_handle_delete on the old\nhandle succeeds in this window, decrements handle_count to 0, and frees\nthe GEM object while the new handle's IDR entry still references it.\n\nNULL the old handle's IDR entry before dropping table_lock so that any\nconcurrent GEM_CLOSE on the old handle sees NULL and returns -EINVAL.\nRestore the old entry on the prime-bookkeeping error path."}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","baseScore":8.8,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:L - Exploitation requires local ioctl calls on /dev/dri/renderD* or /dev/dri/card* through DRM_IOCTL_GEM_CHANGE_HANDLE and DRM_IOCTL_GEM_CLOSE; there is no network-facing path to this code.\nAC:L - The attacker controls both racing threads from the same process (one issuing GEM_CHANGE_HANDLE, one issuing GEM_CLOSE on the old handle) and can repeat until the window is hit; this is a self-induced race, not one dependent on external timing.\nPR:L - Only DRM_RENDER_ALLOW is required, available to unprivileged local users with access to a render node (common on desktops, Android, browsers' GPU processes, and cloud GPU instances); no CAP_SYS_ADMIN or init-namespace root is needed.\nUI:N - No victim interaction is required beyond the attacker already having render-node access; the race is triggered entirely by the attacker's own concurrent ioctl calls.\nS:C - Successful exploitation crosses from a sandboxed application security boundary (browser GPU process, Android app sandbox, or container with passed-through GPU device) into kernel memory, enabling privilege escalation beyond the attacker's original security scope.\nC:H - The bug is a GEM object use-after-free; freed kernel heap objects can be reallocated and dereferenced via subsequent GEM operations, enabling arbitrary kernel memory disclosure.\nI:H - Use-after-free of a drm_gem_object allows heap grooming and corruption of reallocated objects, providing a standard path to arbitrary kernel write and local privilege escalation/code execution.\nA:H - The race can free a GEM object still referenced by ioctl state, causing kernel oops/panic on dereference of freed memory; UAF bugs also carry inherent crash risk even before full exploitation."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/gpu/drm/drm_gem.c"],"versions":[{"version":"672464dd53231509c9c771110798c56d4660e19e","lessThan":"0dfa42cfe4dbe114533480503934f43e33c1e83d","status":"affected","versionType":"git"},{"version":"61bd96d3e5472c253f9c1ab77608f0c8aaa9d025","lessThan":"cde2c9257cbe8463b9dcf7b1075177b72b5fd938","status":"affected","versionType":"git"},{"version":"5e28b7b94408897e41c63477aabc9e1db439bc8c","lessThan":"7164d78559b0ff29931a366a840a9e5dd53d4b7c","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/gpu/drm/drm_gem.c"],"versions":[{"version":"6.18.32","lessThan":"6.18.35","status":"affected","versionType":"semver"},{"version":"7.0.9","lessThan":"7.0.12","status":"affected","versionType":"semver"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.18.32","versionEndExcluding":"6.18.35"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"7.0.9","versionEndExcluding":"7.0.12"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/0dfa42cfe4dbe114533480503934f43e33c1e83d"},{"url":"https://git.kernel.org/stable/c/cde2c9257cbe8463b9dcf7b1075177b72b5fd938"},{"url":"https://git.kernel.org/stable/c/7164d78559b0ff29931a366a840a9e5dd53d4b7c"}],"title":"drm/gem: fix race between change_handle and handle_delete","x_generator":{"engine":"bippy-1.2.0"}}}}