CVE-2026-63863
Linux drm/gpusvm unbalanced unlock can trigger kernel oops/DoS
Is CVE-2026-63863 being exploited?
Not confirmed. CVE-2026-63863 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.12% probability of exploitation in the next 30 days.
How severe is CVE-2026-63863?
CVE-2026-63863 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-63863?
Yes. A fix has been recorded for CVE-2026-63863. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-63863 affect?
CVE-2026-63863 affects Linux kernel (drm gpusvm subsystem), Linux distributions using affected kernel builds. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-63863?
Install vendor/mainline kernel update with gpusvm fix and reboot affected hosts
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unbalanced lock in drm_gpusvm can cause kernel oops/panic and memory corruption, enabling denial-of-service and possible privilege escalation from user-space GPU interactions.
Patch when possible
- affected>= f1d08a5864822684773105c60528e2abb577ca6c and < 8efaa47a871662a8c21b819cec60786f7ef17ab4
- affected>= f1d08a5864822684773105c60528e2abb577ca6c and < d287dee565c3c32e1ed76ec1847af46809c29b90
- affected7.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.