In the Linux kernel, the following vulnerability has been resolved: drm/colorop: Fix blob property reference tracking in state lifecycle The colorop… (CVE-2026-53378)
A vulnerability in the Linux kernel's drm/colorop component caused memory leaks due to improper handling of blob property references during state duplication, destruction, and reset operations. The issue was that the code did not correctly follow the reference counting pattern established by drm_crtc, leading to leaks when freeing or resetting state memory. The fix involved adding a helper function to properly release blob references and updating the relevant functions to use this helper, ensuring correct lifecycle management of state blobs.
AI Analysis
Technical Summary
The Linux kernel's drm/colorop subsystem had a vulnerability involving memory leaks caused by incorrect reference tracking of blob properties in the state lifecycle. Specifically, drm_colorop_atomic_destroy_state() freed state memory without releasing blob references, drm_colorop_reset() improperly freed old state memory directly, and drm_colorop_cleanup() contained duplicate cleanup code. The fix introduced a helper function __drm_atomic_helper_colorop_destroy_state() to correctly release blob references before freeing memory and updated the affected functions to use this helper, aligning with the well-tested drm_crtc pattern since 2016. This correction ensures proper reference counting and prevents memory leaks during state duplication, destruction, and reset operations.
Potential Impact
The vulnerability leads to memory leaks in the Linux kernel's drm/colorop component during state lifecycle operations. While memory leaks can degrade system stability or performance over time, no direct exploitation or other impacts such as privilege escalation or code execution are indicated. There are no known exploits in the wild for this issue.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this vulnerability by properly managing blob property references during state lifecycle operations. Users should apply the official kernel updates that include this fix once available. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor or Linux kernel advisory for the current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: drm/colorop: Fix blob property reference tracking in state lifecycle The colorop… (CVE-2026-53378)
Description
A vulnerability in the Linux kernel's drm/colorop component caused memory leaks due to improper handling of blob property references during state duplication, destruction, and reset operations. The issue was that the code did not correctly follow the reference counting pattern established by drm_crtc, leading to leaks when freeing or resetting state memory. The fix involved adding a helper function to properly release blob references and updating the relevant functions to use this helper, ensuring correct lifecycle management of state blobs.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's drm/colorop subsystem had a vulnerability involving memory leaks caused by incorrect reference tracking of blob properties in the state lifecycle. Specifically, drm_colorop_atomic_destroy_state() freed state memory without releasing blob references, drm_colorop_reset() improperly freed old state memory directly, and drm_colorop_cleanup() contained duplicate cleanup code. The fix introduced a helper function __drm_atomic_helper_colorop_destroy_state() to correctly release blob references before freeing memory and updated the affected functions to use this helper, aligning with the well-tested drm_crtc pattern since 2016. This correction ensures proper reference counting and prevents memory leaks during state duplication, destruction, and reset operations.
Potential Impact
The vulnerability leads to memory leaks in the Linux kernel's drm/colorop component during state lifecycle operations. While memory leaks can degrade system stability or performance over time, no direct exploitation or other impacts such as privilege escalation or code execution are indicated. There are no known exploits in the wild for this issue.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this vulnerability by properly managing blob property references during state lifecycle operations. Users should apply the official kernel updates that include this fix once available. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor or Linux kernel advisory for the current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-2r25-qjcv-hr44
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-53378"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27ad2a4a8d59891325dc
Added to database: 07/19/2026, 19:38:21 UTC
Last enriched: 07/19/2026, 20:25:05 UTC
Last updated: 07/20/2026, 17:26:47 UTC
Views: 13
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.