Answer in brief
CVE-2026-52966 records a Unknown severity vulnerability in drm: Replace old pointer to new idr. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=672464dd53231509c9c771110798c56d4660e19e <318b995cffcfcaa69a234d28123a3f4ae186a9df || >=61bd96d3e5472c253f9c1ab77608f0c8aaa9d025 <38f12d0e10d83b66fa1466400d876a3a8da31542 || >=5e28b7b94408897e41c63477aabc9e1db439bc8c <dc366607c41c45fd0ae6f3db090f31dd611b644a | 318b995cffcfcaa69a234d28123a3f4ae186a9df, 38f12d0e10d83b66fa1466400d876a3a8da31542, dc366607c41c45fd0ae6f3db090f31dd611b644a |
| Linux/Linuxgeneric | >=6.18.32 <6.18.33 || >=7.0.9 <7.0.10 | 6.18.33, 7.0.10 |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
In the Linux kernel, the following vulnerability has been resolved: drm: Replace old pointer to new idr Commit 5e28b7b94408 introduced a logical error by failing to replace the newly generated IDR pointer to old id's pointer at the correct location within the "change handle" logic; this resulted in the issue reported by syzbot [1]. Specifically, the new IDR object pointer is intended to replace the original id's pointer during the normal execution flow. Additionally, an unnecessary conditional check for the ret exit path has been removed. [1] !RB_EMPTY_ROOT(&prime_fpriv->dmabufs) WARNING: drivers/gpu/drm/drm_prime.c:224 at drm_prime_destroy_file_private+0x48/0x60 drivers/gpu/drm/drm_prime.c:224, CPU#0: syz.0.17/5833 Call Trace: drm_file_free.part.0+0x7e6/0xcc0 drivers/gpu/drm/drm_file.c:269 drm_file_free drivers/gpu/drm/drm_file.c:237 [inline] drm_close_helper.isra.0+0x186/0x200 drivers/gpu/drm/drm_file.c:290 drm_release+0x1ab/0x360 drivers/gpu/drm/drm_file.c:438
Quoted source text, attributed separately from HOL analysis.