CVE-2026-63844

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 v4.0.3 ring

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

(cherry picked from commit 2f6afc97d259d530f4f86c7743efbc573a8da927)

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

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

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

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

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

https://git.kernel.org/stable/c/8549b3933038e68dc61cb934b9a54223dd244a78
generic

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

https://git.kernel.org/stable/c/83e37c0987ca92f9e87789b46dd311dcf5a4a6c8
generic

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

https://git.kernel.org/stable/c/249fa7549736de1c8e327d7ca6b32fa148a40bd6

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

Frequently asked(5)

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

Explore →

Is Your Infrastructure Affected by CVE-2026-63844?

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