# drm: Replace old pointer to new idr

CVE record · `CVE-2026-52966`

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

Published by the CVE Program (CNA: Linux) at 24 Jun 2026, 16:28 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: `672464dd53231509c9c771110798c56d4660e19e to before 318b995cffcfcaa69a234d28123a3f4ae186a9df` (git)
  - affected: `61bd96d3e5472c253f9c1ab77608f0c8aaa9d025 to before 38f12d0e10d83b66fa1466400d876a3a8da31542` (git)
  - affected: `5e28b7b94408897e41c63477aabc9e1db439bc8c to before dc366607c41c45fd0ae6f3db090f31dd611b644a` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.18.32 to before 6.18.33` (semver)
  - affected: `7.0.9 to before 7.0.10` (semver)
  - Other versions: unaffected

## Machine-written summary

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

> The Linux kernel DRM code is affected in 6.18.32 before 6.18.33 and 7.0.9 before 7.0.10, plus older ranges. A logic error leaves a stale IDR pointer, causing a kernel warning when a DRM file is closed. The source gives few details on attacker access or wider impact; upgrade to 6.18.33, 7.0.10, 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.0017, the 6th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 24 Jun 2026, 16:28 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-52966)
- 24 Jun 2026, 17:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-52966)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/318b995cffcfcaa69a234d28123a3f4ae186a9df>
- <https://git.kernel.org/stable/c/38f12d0e10d83b66fa1466400d876a3a8da31542>
- <https://git.kernel.org/stable/c/dc366607c41c45fd0ae6f3db090f31dd611b644a>

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-52966>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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