CVE-2026-63852

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 v4.0.3 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 ff1a5a125c5a70c328806b9bc01d7d942cf3f9aa)

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 v4.0.3 enc ring - kernel/git/stable/linux.git - Linux kernel stable tree

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

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

https://git.kernel.org/stable/c/9076a83e5adefd10dc5c967c7b8bde601c4c512a
generic

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

https://git.kernel.org/stable/c/4532b52b34e4e4310386e6fdf6a643368599f522
generic

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

https://git.kernel.org/stable/c/387b7c7667bd5c53549350ddad866d2fcf75a529
generic

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

https://git.kernel.org/stable/c/0177ac6141c8857130cf365369c74dee7b6b1f7f

Vendor Advisories for CVE-2026-63852(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

(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

(18)

Data Freshness Timeline

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

Frequently asked(5)

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

Explore →

Is Your Infrastructure Affected by CVE-2026-63852?

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