CVE-2026-53378
MEDIUMDescription
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.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 1% of all known CVEs.
References
Related Vulnerabilities
Other CWE-401 (Missing Release of Memory (Memory Leak)) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2020-13934 | High | 7.5 | 64% | - | Fix |
| CVE-2016-6304 | High | 7.5 | 63% | - | Fix |
| CVE-2019-12265 | Medium | 5.3 | 60% | - | Fix |
| CVE-2001-0136 | Medium | 5.0 | 45% | - | - |
| CVE-2016-4232 | High | 7.5 | 36% | - | - |
| CVE-2001-0543 | Medium | 5.0 | 19% | - | - |
Common questions
How do I fix CVE-2026-53378?
Published advisories record a fix for 6 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2026-53378 being actively exploited?
Not that we know of. CVE-2026-53378 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.11% is the estimated probability that it will be exploited in the next 30 days. That is higher than 1% of all scored CVEs.
How severe is CVE-2026-53378?
CVE-2026-53378 has a CVSS v3 base score of 5.5, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-53378 affect?
Published advisories record a fix for linux (Debian), linux-image-7.0.0-1016-nvidia (Ubuntu), linux-image-7.0.0-1016-nvidia-64k (Ubuntu), linux-image-nvidia-64k-7.0 (Ubuntu), and 2 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-53378
Markdown
[](https://tridentstack.com/cve/CVE-2026-53378)HTML
<a href="https://tridentstack.com/cve/CVE-2026-53378"><img src="https://tridentstack.com/cve/badge/CVE-2026-53378.svg" alt="CVE-2026-53378"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-07-29.