CVE-2026-63850

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
7.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: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu/vcn: set no_user_fence for VCN v5.0.0 enc ring

VCN encoder and decoder rings do not support 64-bit user fence writes, reject CS submissions with user fences.

(cherry picked from commit 49b1fbbb5a071197ee71e2d70959b1cb29bdc317)

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (4)

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

drm/amdgpu/vcn: set no_user_fence for VCN v5.0.0 enc ring - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9f5a1459ecc3195282be617639d710b54779c9dc
generic

drm/amdgpu/vcn: set no_user_fence for VCN v5.0.0 enc ring - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8cae0ce77de492d7c31c1532a2e80c0c6e7e58cb
generic

drm/amdgpu/vcn: set no_user_fence for VCN v5.0.0 enc ring - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2c350f3cd94be847ac216e1358ec7001eaaf0934
generic

drm/amdgpu/vcn: set no_user_fence for VCN v5.0.0 enc ring - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/139a8a52ef4349c62129703b3a3e3a6ae4d634eb

Vendor Advisories for CVE-2026-63850(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-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
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

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
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 / 173× 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 222 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-63850?
CVE-2026-63850 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/vcn: set nouserfence for VCN v5.0.0 enc ring VCN encoder and decoder rings do not support 64-bit user fence writes, reject CS submissions with user fences. (cherry picked from commit…
When was CVE-2026-63850 disclosed?
CVE-2026-63850 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-63850 actively exploited?
CVE-2026-63850 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 96.2% of all scored CVEs.
What is the CVSS score of CVE-2026-63850?
CVE-2026-63850 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-63850?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63850, 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-63850

Explore →

Is Your Infrastructure Affected by CVE-2026-63850?

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

Start Free Scan →Browse All CVEs