In the Linux kernel, the following vulnerability has been resolved: drm/gpusvm: Fix unbalanced unlock in drm_gpusvm_scan_mm() There is a unbalanced… (CVE-2026-63863)
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.
AI Analysis
Technical Summary
The Linux kernel vulnerability CVE-2026-63863 concerns an unbalanced lock/unlock sequence in the drm/gpusvm subsystem, specifically in the drm_gpusvm_scan_mm() function. The drm_gpusvm_notifier_unlock() function was called under an error handling label (err_free) before the corresponding drm_gpusvm_notifier_lock() was acquired, leading to an attempt to release a lock that was not held. This results in kernel warnings about bad unlock balance and could lead to kernel instability or unexpected behavior. The issue has been resolved by fixing the lock/unlock sequence in the kernel source.
Potential Impact
The vulnerability causes an unbalanced unlock on a kernel lock, which can lead to kernel warnings and potentially unstable kernel behavior. There is no indication of remote code execution or privilege escalation from the provided data. The impact is primarily on kernel stability and correctness.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel source code. Since no explicit patch links or vendor advisories are provided, users should update to the latest Linux kernel versions where this issue is resolved. Patch status is not yet confirmed in the provided data — check the official Linux kernel advisories or source repositories for the fixed version and apply updates accordingly.
In the Linux kernel, the following vulnerability has been resolved: drm/gpusvm: Fix unbalanced unlock in drm_gpusvm_scan_mm() There is a unbalanced… (CVE-2026-63863)
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.
CVSS v3.1
Score 8.8high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel vulnerability CVE-2026-63863 concerns an unbalanced lock/unlock sequence in the drm/gpusvm subsystem, specifically in the drm_gpusvm_scan_mm() function. The drm_gpusvm_notifier_unlock() function was called under an error handling label (err_free) before the corresponding drm_gpusvm_notifier_lock() was acquired, leading to an attempt to release a lock that was not held. This results in kernel warnings about bad unlock balance and could lead to kernel instability or unexpected behavior. The issue has been resolved by fixing the lock/unlock sequence in the kernel source.
Potential Impact
The vulnerability causes an unbalanced unlock on a kernel lock, which can lead to kernel warnings and potentially unstable kernel behavior. There is no indication of remote code execution or privilege escalation from the provided data. The impact is primarily on kernel stability and correctness.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel source code. Since no explicit patch links or vendor advisories are provided, users should update to the latest Linux kernel versions where this issue is resolved. Patch status is not yet confirmed in the provided data — check the official Linux kernel advisories or source repositories for the fixed version and apply updates accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-6jp3-p375-g5x4
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-63863"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- 3.1
Threat ID: 6a5d27ac2a4a8d5989130c76
Added to database: 07/19/2026, 19:38:20 UTC
Last enriched: 07/19/2026, 20:16:12 UTC
Last updated: 09/02/2026, 10:52:10 UTC
Views: 56
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.