CVE-2026-63863

drm/gpusvm: Fix unbalanced unlock in drm_gpusvm_scan_mm()

Published Jul 19, 2026 CVSS 3.1 · 8.8 High EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

drm/gpusvm: Fix unbalanced unlock in drm_gpusvm_scan_mm()

There is a unbalanced lock/unlock to gpusvm notifier lock:
[ 931.045868] =====================================
[ 931.046509] WARNING: bad unlock balance detected!
[ 931.047149] 6.19.0-rc6+xe-**************** #9 Tainted: G U
[ 931.048150] -------------------------------------
[ 931.048790] kworker/u5:0/51 is trying to release lock (&gpusvm->notifier_lock) at:
[ 931.049801] [<ffffffffa090c0d8>] drm_gpusvm_scan_mm+0x188/0x460 [drm_gpusvm_helper]
[ 931.050802] but there are no more locks to release!
[ 931.051463]

The drm_gpusvm_notifier_unlock() sits under err_free label and the
first jump to err_free is just before calling the
drm_gpusvm_notifier_lock() causing unbalanced unlock.

Analysis

AI-generated

Technical impact

An unbalanced unlock in the gpusvm notifier lock can expose the Linux kernel to a lock state inconsistency. It is inferred from the description that an unbalanced unlock could potentially lead to a kernel panic or other instability. The problem originates from an unlock performed without a matching lock in drm_gpusvm_scan_mm(), which is a type of improper synchronization and lock/unlock weakness (CWE-832 and CWE-667).

Affected Systems

All Linux kernel releases that include the gpusvm notifier code prior to the commit that implements the fix (8efaa47a871662a8c21b819cec60786f7ef17ab4) are affected. Since no specific version range is supplied, every kernel version up to and including the 6.19.0-rc6+ build shown in the logs should be considered vulnerable until the fix is applied.

Risk and Exploitability

The CVSS score of 8.8 places this issue in the high severity range. The EPSS score of less than 1% indicates a very low probability of exploitation at the present time, and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector is inferred from the description to involve user space code that interacts with the GPU driver, which may trigger the bad unlock condition. While an exploit has not been documented, the high severity and kernel privilege escalation inherent in the flaw make it a critical remediation candidate.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply a kernel update that incorporates the commit 8efaa47a871662a8c21b819cec60786f7ef17ab4 or a later that contains the fix
  • If updating cannot be performed immediately, disable GPU virtualization features that invoke gpusvm_scan_mm(), such as disabling or unloading the GPU driver or configuring the system to prevent GPU VM usage
  • Restrict GPU device access to trusted users by setting appropriate file system permissions or using device cgroups so that only authorized processes can communicate with GPU resources

Generated by OpenCVE AI on October 20, 2026 at 08:44 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8593-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8603-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8618-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8663-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8664-1 Linux kernel (NVIDIA BaseOS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-1 Linux kernel (GCP) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-2 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-3 Linux kernel (Oracle) vulnerabilities
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-667
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H'}

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: drm/gpusvm: Fix unbalanced unlock in drm_gpusvm_scan_mm() There is a unbalanced lock/unlock to gpusvm notifier lock: [ 931.045868] ===================================== [ 931.046509] WARNING: bad unlock balance detected! [ 931.047149] 6.19.0-rc6+xe-**************** #9 Tainted: G U [ 931.048150] ------------------------------------- [ 931.048790] kworker/u5:0/51 is trying to release lock (&gpusvm->notifier_lock) at: [ 931.049801] [<ffffffffa090c0d8>] drm_gpusvm_scan_mm+0x188/0x460 [drm_gpusvm_helper] [ 931.050802] but there are no more locks to release! [ 931.051463] The drm_gpusvm_notifier_unlock() sits under err_free label and the first jump to err_free is just before calling the drm_gpusvm_notifier_lock() causing unbalanced unlock.
Title drm/gpusvm: Fix unbalanced unlock in drm_gpusvm_scan_mm()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-667

    Improper Locking

  • CWE-832

    Unlock of a Resource that is not Locked

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 19, 2026, 8:17 PM
Reserved
Jul 19, 2026, 7:54 AM
Status
Analyzed
Published
Jul 19, 2026, 3:16 PM
Modified
Oct 26, 2026, 5:00 PM
Severity
Moderate
Public date
Jul 19, 2026, 12:00 AM