CVE-2026-63846

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/jpeg: set no_user_fence for JPEG v3.0 ring

JPEG rings do not support 64-bit user fence writes, reject CS submissions with user fences.

(cherry picked from commit 4d7d774f100efb5089c86a1fb8c5bf47c63fc9ef)

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 (5)

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

drm/amdgpu/jpeg: set no_user_fence for JPEG v3.0 ring - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdgpu/jpeg: set no_user_fence for JPEG v3.0 ring - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdgpu/jpeg: set no_user_fence for JPEG v3.0 ring - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdgpu/jpeg: set no_user_fence for JPEG v3.0 ring - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/48ce00787e3fddd2b45692fc991b8ab128343da5
generic

drm/amdgpu/jpeg: set no_user_fence for JPEG v3.0 ring - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/303da8279f195cc741adc52c1b44d6b64de63bb0

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

Frequently asked(5)

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

Explore →

Is Your Infrastructure Affected by CVE-2026-63846?

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