An unbalanced unlock in the gpusvm notifier lock can cause the Linux kernel to detect a bad unlock balance warning and potentially crash. The flaw originates from a missing corresponding lock before an unlock in drm_gpusvm_scan_mm(), leading to inconsistent lock state that may trigger a kernel panic. The vulnerability is a type of improper synchronization weakness (CWE‑832).

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.

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. Based on the description, the likely attack vector involves code that interacts with the GPU driver from user space, so a local or privileged user with access to the GPU subsystem could potentially trigger the bad unlock condition and cause a kernel panic. While an exploit has not been documented, the high severity and kernel privilege escalation inherent in the flaw make it a critical remediation candidate.