# drm/colorop: Fix blob property reference tracking in state lifecycle

CVE record · `CVE-2026-53378`

- **Identifiers:** `CVE-2026-53378`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 19 Jul 2026
- **Updated:** 6 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 19 Jul 2026, 10:02 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `cfc27680ee208cdf7a61cda817b4158c4142595f to before 271059f1d9020e9ac967524e319fbbaa22d0475b` (git)
  - affected: `cfc27680ee208cdf7a61cda817b4158c4142595f to before 235b333e2878d791cee09e1e72f44611a9400114` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.19`
  - unaffected: `before 6.19` (semver)
  - unaffected: `7.0.9 to 7.0.*, inclusive` (semver)
  - unaffected: `7.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel DRM colorop code (version 6.19) leaks blob property references during colorop state duplication, destruction, and reset, causing memory leaks. The source gives few details on what an attacker could do with this. Upgrade to 7.0.9 or later in the 7.0 series, or to 7.1 or later.

Written 17 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0014, the 3rd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 19 Jul 2026, 10:02 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-53378)
- 19 Jul 2026, 11:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-53378)

## Sources

- [CVE List: CVE-2026-53378](https://www.cve.org/CVERecord?id=CVE-2026-53378)
- [NVD: CVE-2026-53378](https://nvd.nist.gov/vuln/detail/CVE-2026-53378)

### References from the CNA

- <https://git.kernel.org/stable/c/271059f1d9020e9ac967524e319fbbaa22d0475b>
- <https://git.kernel.org/stable/c/235b333e2878d791cee09e1e72f44611a9400114>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-53378>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-53378/>. Everything for agents: <https://agentprime.io/llms.txt>.
