CVE-2026-53313

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-26. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

drm/amd/display: Avoid NULL dereference in dc_dmub_srv error paths

In dc_dmub_srv_log_diagnostic_data() and dc_dmub_srv_enable_dpia_trace().

Both functions check:

if (!dc_dmub_srv || !dc_dmub_srv->dmub)

and then call DC_LOG_ERROR() inside that block.

DC_LOG_ERROR() uses dc_dmub_srv->ctx internally. So if dc_dmub_srv is NULL, the logging itself can dereference a NULL pointer and cause a crash.

Fix this by splitting the checks.

First check if dc_dmub_srv is NULL and return immediately. Then check dc_dmub_srv->dmub and log the error only when dc_dmub_srv is valid.

Fixes the below: ../display/dc/dc_dmub_srv.c:962 dc_dmub_srv_log_diagnostic_data() error: we previously assumed 'dc_dmub_srv' could be null (see line 961) ../display/dc/dc_dmub_srv.c:1167 dc_dmub_srv_enable_dpia_trace() error: we previously assumed 'dc_dmub_srv' could be null (see line 1166)

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

June 26, 2026

Last Modified

September 7, 2026

Advisory Details (2)

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

drm/amd/display: Avoid NULL dereference in dc_dmub_srv error paths - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amd/display: Avoid NULL dereference in dc_dmub_srv error paths - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4ae3e16f4b3bf64140f773629b765d605ee079a9

Vendor Advisories for CVE-2026-53313(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-07ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-07ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-07ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-07ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-09-07ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-07ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-09-07ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-07ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-07ubuntu

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (353 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (176 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(9)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 13× in last 7d / 69× 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 176 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53313?
CVE-2026-53313 is a medium vulnerability published on June 26, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Avoid NULL dereference in dcdmubsrv error paths In dcdmubsrvlogdiagnostic_data() and dcdmubsrvenabledpia_trace(). Both functions check: if (!dcdmubsrv || !dcdmubsrv->dmub) and then call DCLOGERROR() inside that…
When was CVE-2026-53313 disclosed?
CVE-2026-53313 was first published in the National Vulnerability Database on June 26, 2026, with the most recent update on September 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53313 actively exploited?
CVE-2026-53313 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 98.3% of all scored CVEs.
What is the CVSS score of CVE-2026-53313?
CVE-2026-53313 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53313?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53313, 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-53313

Explore →

Is Your Infrastructure Affected by CVE-2026-53313?

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

Start Free Scan →Browse All CVEs