CVE-2026-53378

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-19. 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/colorop: Fix blob property reference tracking in state lifecycle

The colorop state blob property handling had memory leaks during state duplication, destruction, and reset operations. The implementation failed to follow the established pattern from drm_crtc's handling of DEGAMMA/GAMMA blob properties.

Issues fixed:

  • drm_colorop_atomic_destroy_state() was freeing state memory without
releasing the blob reference, causing a leak
  • drm_colorop_reset() was directly freeing old state with kfree()
instead of properly destroying it, leaking blob references
  • drm_colorop_cleanup() had duplicate blob cleanup code

Changes:

  • Add __drm_atomic_helper_colorop_destroy_state() helper to properly
release blob references before freeing state memory
  • Update drm_colorop_atomic_destroy_state() to call the helper
  • Fix drm_colorop_reset() to use drm_colorop_atomic_destroy_state()
for proper cleanup of old state
  • Simplify drm_colorop_cleanup() to use the common destruction path

This matches the well-tested pattern used by drm_crtc since 2016 and ensures proper reference counting throughout the state lifecycle.

Co-developed by Claude Sonnet 4.5.

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

July 19, 2026

Last Modified

July 29, 2026

Advisory Details (2)

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

drm/colorop: Fix blob property reference tracking in state lifecycle - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/271059f1d9020e9ac967524e319fbbaa22d0475b
generic

drm/colorop: Fix blob property reference tracking in state lifecycle - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/235b333e2878d791cee09e1e72f44611a9400114

Vendor Advisories for CVE-2026-53378(1)

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

Patch Availability(6)

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

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 (138 versions)7.0.9-1—

Weakness Classification(1)

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

All Vendor Advisories

(6)

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 12× in last 7d / 64× 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 168 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53378?
CVE-2026-53378 is a medium vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/colorop: Fix blob property reference tracking in state lifecycle The colorop state blob property handling had memory leaks during state duplication, destruction, and reset operations. The implementation failed to follow the…
When was CVE-2026-53378 disclosed?
CVE-2026-53378 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on July 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53378 actively exploited?
CVE-2026-53378 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.5% of all scored CVEs.
What is the CVSS score of CVE-2026-53378?
CVE-2026-53378 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53378?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53378, 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-53378

Explore →

Is Your Infrastructure Affected by CVE-2026-53378?

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

Start Free Scan →Browse All CVEs