CVE-2026-63863

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

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] [] 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
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (2)

Auto-updated Jul 20, 2026
No patch confirmed yet.
generic

drm/gpusvm: Fix unbalanced unlock in drm_gpusvm_scan_mm() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d287dee565c3c32e1ed76ec1847af46809c29b90
generic

drm/gpusvm: Fix unbalanced unlock in drm_gpusvm_scan_mm() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8efaa47a871662a8c21b819cec60786f7ef17ab4

Vendor Advisories for CVE-2026-63863(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (137 versions)7.0.10-1—

All Vendor Advisories

(5)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 32× in last 7d / 161× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 269 total refreshes for this CVE.

  1. 2026-08-30 03:00 UTCEG score recompute
  2. 2026-08-30 03:00 UTCVendor advisory
  3. 2026-08-30 03:00 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-27 23:50 UTCEG score recompute
  7. 2026-08-27 23:50 UTCVendor advisory
  8. 2026-08-27 23:50 UTCGHSA enrichment
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-27 11:55 UTCVendor advisory
  11. 2026-08-27 11:55 UTCGHSA enrichment
  12. 2026-08-26 22:28 UTCEG score recompute
  13. 2026-08-26 22:28 UTCVendor advisory
  14. 2026-08-26 22:28 UTCGHSA enrichment
  15. 2026-08-26 14:46 UTCEPSS rescore
  16. 2026-08-26 08:47 UTCVendor advisory
  17. 2026-08-26 08:47 UTCGHSA enrichment
  18. 2026-08-25 20:57 UTCEG score recompute
  19. 2026-08-25 20:57 UTCVendor advisory
  20. 2026-08-25 20:57 UTCGHSA enrichment
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-25 08:39 UTCGHSA enrichment
  23. 2026-08-24 20:51 UTCEG score recompute
  24. 2026-08-24 20:51 UTCVendor advisory
  25. 2026-08-24 20:51 UTCGHSA enrichment
Show 75 more
  1. 2026-08-24 09:07 UTCVendor advisory
  2. 2026-08-24 09:07 UTCGHSA enrichment
  3. 2026-08-23 21:20 UTCVendor advisory
  4. 2026-08-23 21:20 UTCGHSA enrichment
  5. 2026-08-23 09:36 UTCEG score recompute
  6. 2026-08-23 09:36 UTCVendor advisory
  7. 2026-08-23 09:36 UTCGHSA enrichment
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-22 21:52 UTCVendor advisory
  10. 2026-08-22 21:52 UTCGHSA enrichment
  11. 2026-08-22 10:08 UTCVendor advisory
  12. 2026-08-22 10:08 UTCGHSA enrichment
  13. 2026-08-21 22:18 UTCVendor advisory
  14. 2026-08-21 22:18 UTCGHSA enrichment
  15. 2026-08-21 10:26 UTCEG score recompute
  16. 2026-08-21 10:26 UTCVendor advisory
  17. 2026-08-21 10:26 UTCGHSA enrichment
  18. 2026-08-20 22:55 UTCEPSS rescore
  19. 2026-08-20 22:40 UTCVendor advisory
  20. 2026-08-20 22:40 UTCGHSA enrichment
  21. 2026-08-20 10:56 UTCVendor advisory
  22. 2026-08-20 10:56 UTCGHSA enrichment
  23. 2026-08-19 23:12 UTCEG score recompute
  24. 2026-08-19 23:12 UTCVendor advisory
  25. 2026-08-19 23:12 UTCGHSA enrichment
  26. 2026-08-19 17:04 UTCEPSS rescore
  27. 2026-08-19 09:43 UTCVendor advisory
  28. 2026-08-19 09:43 UTCGHSA enrichment
  29. 2026-08-18 21:49 UTCEG score recompute
  30. 2026-08-18 21:49 UTCVendor advisory
  31. 2026-08-18 21:49 UTCGHSA enrichment
  32. 2026-08-18 13:48 UTCEPSS rescore
  33. 2026-08-18 09:27 UTCVendor advisory
  34. 2026-08-18 09:27 UTCGHSA enrichment
  35. 2026-08-17 21:10 UTCEG score recompute
  36. 2026-08-17 21:10 UTCVendor advisory
  37. 2026-08-17 21:10 UTCGHSA enrichment
  38. 2026-08-17 13:47 UTCEPSS rescore
  39. 2026-08-17 06:57 UTCVendor advisory
  40. 2026-08-17 06:57 UTCGHSA enrichment
  41. 2026-08-16 19:14 UTCEG score recompute
  42. 2026-08-16 19:14 UTCVendor advisory
  43. 2026-08-16 19:14 UTCGHSA enrichment
  44. 2026-08-16 14:56 UTCEPSS rescore
  45. 2026-08-16 07:30 UTCEG score recompute
  46. 2026-08-16 07:30 UTCVendor advisory
  47. 2026-08-16 07:30 UTCGHSA enrichment
  48. 2026-08-15 19:47 UTCVendor advisory
  49. 2026-08-15 19:47 UTCGHSA enrichment
  50. 2026-08-15 08:03 UTCEG score recompute
  51. 2026-08-15 08:03 UTCVendor advisory
  52. 2026-08-15 08:03 UTCGHSA enrichment
  53. 2026-08-15 01:30 UTCEPSS rescore
  54. 2026-08-14 20:19 UTCVendor advisory
  55. 2026-08-14 20:19 UTCGHSA enrichment
  56. 2026-08-14 08:36 UTCEG score recompute
  57. 2026-08-14 08:36 UTCVendor advisory
  58. 2026-08-14 08:36 UTCGHSA enrichment
  59. 2026-08-13 22:00 UTCEPSS rescore
  60. 2026-08-13 20:52 UTCVendor advisory
  61. 2026-08-13 20:52 UTCGHSA enrichment
  62. 2026-08-13 09:08 UTCVendor advisory
  63. 2026-08-13 09:08 UTCGHSA enrichment
  64. 2026-08-12 21:24 UTCEG score recompute
  65. 2026-08-12 21:24 UTCVendor advisory
  66. 2026-08-12 21:24 UTCGHSA enrichment
  67. 2026-08-12 13:51 UTCEPSS rescore
  68. 2026-08-12 09:41 UTCVendor advisory
  69. 2026-08-12 09:41 UTCGHSA enrichment
  70. 2026-08-11 21:57 UTCEG score recompute
  71. 2026-08-11 21:57 UTCVendor advisory
  72. 2026-08-11 21:57 UTCGHSA enrichment
  73. 2026-08-11 10:13 UTCEG score recompute
  74. 2026-08-11 10:13 UTCVendor advisory
  75. 2026-08-11 10:13 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-63863?
CVE-2026-63863 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/gpusvm: Fix unbalanced unlock in drmgpusvmscan_mm() There is a unbalanced lock/unlock to gpusvm notifier lock: [ 931.045868] ===================================== [ 931.046509] WARNING: bad unlock balance detected! […
When was CVE-2026-63863 disclosed?
CVE-2026-63863 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63863 actively exploited?
CVE-2026-63863 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.6% of all scored CVEs.
What is the CVSS score of CVE-2026-63863?
CVE-2026-63863 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-63863?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63863, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63863

Explore →

Is Your Infrastructure Affected by CVE-2026-63863?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs