CVE-2026-63855

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 v2.5 enc/dec rings

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

(cherry picked from commit efc9dd5590894109bce9a0bfe1fa5592dd6b20b1)

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
3%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (5)

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

drm/amdgpu/vcn: set no_user_fence for VCN v2.5 enc/dec rings - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdgpu/vcn: set no_user_fence for VCN v2.5 enc/dec rings - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/602d4c5872b25ddd4d82fb2025efb9a05b187bb3
generic

drm/amdgpu/vcn: set no_user_fence for VCN v2.5 enc/dec rings - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5a3c6f76cab164a5d803084908d7050f649ab7f9
generic

drm/amdgpu/vcn: set no_user_fence for VCN v2.5 enc/dec rings - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4f317863a3ab212a027d8c8c3cc3af4e3fb95704
generic

drm/amdgpu/vcn: set no_user_fence for VCN v2.5 enc/dec rings - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2c6fb056567efb49f8674108b86088a1cfaa86d0

Vendor Advisories for CVE-2026-63855(1)

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

Patch Availability(18)

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (335 versions)
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

(18)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-63855?
CVE-2026-63855 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 v2.5 enc/dec rings 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-63855 disclosed?
CVE-2026-63855 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-63855 actively exploited?
CVE-2026-63855 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.9% of all scored CVEs.
What is the CVSS score of CVE-2026-63855?
CVE-2026-63855 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-63855?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63855, 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-63855

Explore →

Is Your Infrastructure Affected by CVE-2026-63855?

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