Skip to main content

Linux Kernel EUVDEUVD-2026-45770

| CVE-2026-63885 HIGH
2026-07-19 Linux GHSA-6335-2wvm-xv3c
8.8
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
8.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
vuln.today AI
7.8 HIGH

Local DRM device access gives AV:L/PR:L; success requires winning a narrow unlock-window race so AC:H; a kernel UAF crossing the user/kernel boundary justifies S:C with full C:H/I:H/A:H.

3.1 AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
HIGH
qualitative
Red Hat
7.0 MEDIUM
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jul 20, 2026 - 16:08 vuln.today
CVSS changed
Jul 20, 2026 - 15:22 NVD
8.8 (HIGH)
Patch available
Jul 19, 2026 - 17:19 EUVD
CVE Published
Jul 19, 2026 - 14:54 cve.org
HIGH 8.8
CVE Published
Jul 19, 2026 - 14:54 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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.

AnalysisAI

Local privilege escalation potential in the Linux kernel's DRM/GEM (Direct Rendering Manager Graphics Execution Manager) subsystem stems from a use-after-free triggered by a race in the drm_gem_change_handle_ioctl path. A local user with access to a DRM device node can race a GEM_CLOSE against a handle-change operation to drop a GEM object's reference count to zero and free it while another handle's IDR entry still points at it, yielding a dangling kernel pointer. No public exploit has been identified at time of analysis and it is not in CISA KEV; EPSS is low (0.20%, 10th percentile), consistent with a local-only race that is non-trivial to weaponize.

Technical ContextAI

The affected component is the DRM GEM buffer-object handle layer, which maps userspace-visible integer handles to kernel GEM objects through a per-file IDR (ID-to-pointer) table protected by table_lock. drm_gem_change_handle_ioctl reassigns an object from an old handle to a new one, but it releases table_lock before nullifying/removing the old IDR slot, leaving the old handle 'live' during the unlock window. The root-cause class is a race condition (CWE-362) leading to a use-after-free (CWE-416); the input lists CWE as N/A and tags it 'Information Disclosure,' but a freed-object dangling pointer in kernel space is broader than pure disclosure. The CPE data only generically identifies cpe:2.3:a:linux:linux, so the precise affected surface is best read from the fix commits touching drm/gem, not the CPE strings.

RemediationAI

Apply the vendor patch by upgrading to a fixed stable kernel: 6.18.35 or later on the 6.18.x branch, or 7.0.12 or later on the 7.0.x branch (Vendor-released patch confirmed via kernel.org stable commits). The fix NULLs the old handle's IDR entry before dropping table_lock so a concurrent GEM_CLOSE sees NULL and returns -EINVAL, and restores the entry on the prime-bookkeeping error path; cherry-pick commits 0dfa42cfe4db, cde2c9257cbe, or 7164d78559b0 if you maintain a custom tree. Where kernel updates cannot be applied immediately, the practical compensating control is to restrict access to DRM device nodes (/dev/dri/card* and renderD*) by tightening group membership (video/render) and limiting untrusted local/interactive users, since exploitation requires local access to those devices - the trade-off is that this can break graphics, GPU compute, and container GPU passthrough for restricted users. There is no network-facing mitigation because the flaw is local-only.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

EUVD-2026-45770 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy