CVE-2026-63854

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 v3.0 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 663bed3c7b8b9a7624b0d95d300ddae034ad0614)

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 v3.0 enc/dec rings - kernel/git/stable/linux.git - Linux kernel stable tree

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

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

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

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

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

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

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

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

https://git.kernel.org/stable/c/26c4f38529ac78930c9c4713e16ebc5b689bb0a3

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

Frequently asked(5)

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

Explore →

Is Your Infrastructure Affected by CVE-2026-63854?

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