CVE-2026-63840

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 v5.3.0 ring

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

(cherry picked from commit 86ac011ae234c03fb872f4945913391ea1d8862e)

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

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

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

https://git.kernel.org/stable/c/46ad73aec27d020f103b4262e4da2d2c22f54799
generic

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

https://git.kernel.org/stable/c/3b0ea2021351b6b813b34fac940957f1f4fad85b

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

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

(1 across 1 ecosystem)
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)

Data Freshness Timeline

(refreshed 30× in last 7d / 159× 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 205 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-63840?
CVE-2026-63840 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 v5.3.0 ring JPEG rings do not support 64-bit user fence writes, reject CS submissions with user fences. (cherry picked from commit 86ac011ae234c03fb872f4945913391ea1d8862e)
When was CVE-2026-63840 disclosed?
CVE-2026-63840 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-63840 actively exploited?
CVE-2026-63840 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-63840?
CVE-2026-63840 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-63840?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63840, 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-63840

Explore →

Is Your Infrastructure Affected by CVE-2026-63840?

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