CVE-2026-63863·Kernel vulnerability
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.
- Severity
- high
- Software
- Kernel
- Fixed in
- 7.0.10
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.13% — higher than 2% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-63863 scores 8.8 on CVSS, so a successful attack would be serious — but at 0.13%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 7.0
Until: 7.0.10
Fixed in: 7.0.10
How to fix this CVE
Update your Linux kernel to version 7.0.10 or later to resolve a critical lock management issue in the DRM GPU shared virtual memory subsystem. This vulnerability causes a kernel warning when the GPU memory scanning function improperly handles lock/unlock sequences, potentially leading to system instability. Apply the patch immediately to prevent denial of service conditions in GPU-heavy workloads.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your current kernel version with `uname -r` and compare against version 7.0.10
- Step 2: Verify if the GPU virtualization subsystem is loaded with `lsmod | grep -i gpusvm` or `lsmod | grep -i drm`
- Step 3: Search kernel logs for the unbalanced lock warning pattern with `dmesg | grep -i 'bad unlock balance' && dmesg | grep -i 'drm_gpusvm_scan_mm'`
- Step 4: After patching, reboot and confirm the new kernel version with `uname -r`, then verify no lock warnings appear in a fresh `dmesg` output
FAQ
What is CVE-2026-63863?
This vulnerability exists in the Linux kernel's Direct Rendering Manager (DRM) GPU shared virtual memory handler, where the drm_gpusvm_scan_mm() function fails to properly balance lock and unlock operations on the notifier lock, causing kernel warnings and potential system instability.
Is CVE-2026-63863 being actively exploited?
No, this vulnerability is not listed on the CISA KEV catalog and no public exploits are available. However, it can cause denial of service through kernel warnings and should still be patched promptly.
What versions of Kernel are affected by CVE-2026-63863?
Linux kernel versions 7.0 through 7.0.9 are affected. Kernel 7.0.10 and later contain the fix.
How do I check if my server is vulnerable to CVE-2026-63863?
Run `uname -r` to display your kernel version and confirm it is below 7.0.10. If your version is 7.0.0 through 7.0.9, your system is vulnerable.
Does Defensia detect CVE-2026-63863?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2026-63863 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-63863. Free for 1 server.
Get started free