CVE-2026-46215

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-28. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

drm: Set old handle to NULL before prime swap in change_handle

There was a potential race condition in change_handle. The ioctl briefly had a single object with two idr entries; a concurrent gem_close could delete the object and remove one of the handles while leaving the other one dangling, which could subsequently be dereferenced for a use-after-free.

To fix this, do the same dance that gem_close itself does. (f6cd7daecff5 drm: Release driver references to handle before making it available again) First idr_replace the old handle to NULL. Later, if the prime operations are successful, actually close it.

create_tail required a similar dance to avoid a similar problem. (bd46cece51a3 drm/gem: Fix race in drm_gem_handle_create_tail()) It idr_allocs the new handle with NULL, then swaps in the correct object later to avoid races. We don't need to do that here, since the only operations that could race are drm_prime, and change_handle holds the prime lock for the entire duration.

v2: cleanups of error paths

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
3.3%
KEV
Not listed

Published

May 28, 2026

Last Modified

July 10, 2026

Advisory Details (3)

Auto-updated Jun 4, 2026
No patch confirmed yet.
generic

drm: Set old handle to NULL before prime swap in change_handle - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/672464dd53231509c9c771110798c56d4660e19e
generic

drm: Set old handle to NULL before prime swap in change_handle - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/61bd96d3e5472c253f9c1ab77608f0c8aaa9d025
generic

drm: Set old handle to NULL before prime swap in change_handle - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5e28b7b94408897e41c63477aabc9e1db439bc8c

Vendor Advisories for CVE-2026-46215(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 70× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 165 total refreshes for this CVE.

  1. 2026-07-16 10:18 UTCEG score recompute
  2. 2026-07-16 10:18 UTCGHSA enrichment
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-13 22:30 UTCEPSS rescore
  6. 2026-07-11 20:48 UTCEG score recompute
  7. 2026-07-11 20:47 UTCGHSA enrichment
  8. 2026-07-11 08:27 UTCEPSS rescore
  9. 2026-07-09 19:10 UTCEPSS rescore
  10. 2026-07-08 18:18 UTCEG score recompute
  11. 2026-07-08 18:18 UTCGHSA enrichment
  12. 2026-07-08 15:16 UTCEPSS rescore
  13. 2026-07-07 13:46 UTCEPSS rescore
  14. 2026-07-06 16:27 UTCEPSS rescore
  15. 2026-07-06 02:23 UTCEPSS rescore
  16. 2026-07-04 06:31 UTCEPSS rescore
  17. 2026-07-02 14:12 UTCEG score recompute
  18. 2026-07-02 14:12 UTCGHSA enrichment
  19. 2026-07-01 15:12 UTCEG score recompute
  20. 2026-07-01 15:11 UTCGHSA enrichment
  21. 2026-07-01 15:07 UTCEPSS rescore
  22. 2026-07-01 03:06 UTCEG score recompute
  23. 2026-07-01 03:06 UTCGHSA enrichment
  24. 2026-06-30 23:22 UTCEPSS rescore
  25. 2026-06-30 01:55 UTCEG score recompute
Show 75 more
  1. 2026-06-30 01:55 UTCGHSA enrichment
  2. 2026-06-29 14:06 UTCEPSS rescore
  3. 2026-06-29 14:06 UTCEPSS rescore
  4. 2026-06-29 13:43 UTCEG score recompute
  5. 2026-06-29 13:43 UTCGHSA enrichment
  6. 2026-06-28 18:43 UTCEG score recompute
  7. 2026-06-28 18:43 UTCGHSA enrichment
  8. 2026-06-28 14:07 UTCEPSS rescore
  9. 2026-06-28 06:37 UTCEG score recompute
  10. 2026-06-28 06:37 UTCGHSA enrichment
  11. 2026-06-28 04:56 UTCEPSS rescore
  12. 2026-06-28 04:56 UTCEPSS rescore
  13. 2026-06-27 18:11 UTCEG score recompute
  14. 2026-06-27 18:11 UTCGHSA enrichment
  15. 2026-06-27 05:26 UTCEG score recompute
  16. 2026-06-27 05:26 UTCGHSA enrichment
  17. 2026-06-27 03:08 UTCEPSS rescore
  18. 2026-06-26 16:50 UTCEG score recompute
  19. 2026-06-26 16:50 UTCGHSA enrichment
  20. 2026-06-25 20:22 UTCEG score recompute
  21. 2026-06-25 20:22 UTCGHSA enrichment
  22. 2026-06-25 13:49 UTCEPSS rescore
  23. 2026-06-25 08:18 UTCEG score recompute
  24. 2026-06-25 08:17 UTCGHSA enrichment
  25. 2026-06-24 16:56 UTCEG score recompute
  26. 2026-06-24 16:56 UTCGHSA enrichment
  27. 2026-06-24 14:05 UTCEPSS rescore
  28. 2026-06-23 21:33 UTCEPSS rescore
  29. 2026-06-23 21:33 UTCEPSS rescore
  30. 2026-06-22 14:25 UTCEPSS rescore
  31. 2026-06-22 14:25 UTCEPSS rescore
  32. 2026-06-21 14:56 UTCEPSS rescore
  33. 2026-06-21 14:56 UTCEPSS rescore
  34. 2026-06-21 01:59 UTCEPSS rescore
  35. 2026-06-21 01:59 UTCEPSS rescore
  36. 2026-06-19 19:26 UTCEPSS rescore
  37. 2026-06-19 19:26 UTCEPSS rescore
  38. 2026-06-18 17:52 UTCEPSS rescore
  39. 2026-06-18 17:52 UTCEPSS rescore
  40. 2026-06-17 18:12 UTCEG score recompute
  41. 2026-06-17 18:12 UTCGHSA enrichment
  42. 2026-06-17 17:53 UTCEPSS rescore
  43. 2026-06-17 03:53 UTCEG score recompute
  44. 2026-06-17 03:53 UTCGHSA enrichment
  45. 2026-06-16 17:52 UTCEPSS rescore
  46. 2026-06-16 15:46 UTCEG score recompute
  47. 2026-06-16 15:46 UTCGHSA enrichment
  48. 2026-06-16 03:41 UTCEG score recompute
  49. 2026-06-16 03:41 UTCGHSA enrichment
  50. 2026-06-15 17:49 UTCEPSS rescore
  51. 2026-06-15 15:36 UTCEG score recompute
  52. 2026-06-15 15:36 UTCGHSA enrichment
  53. 2026-06-15 03:31 UTCEG score recompute
  54. 2026-06-15 03:31 UTCGHSA enrichment
  55. 2026-06-14 15:26 UTCEG score recompute
  56. 2026-06-14 15:26 UTCGHSA enrichment
  57. 2026-06-14 03:21 UTCEG score recompute
  58. 2026-06-14 03:21 UTCGHSA enrichment
  59. 2026-06-13 23:00 UTCEPSS rescore
  60. 2026-06-13 15:13 UTCEG score recompute
  61. 2026-06-13 15:13 UTCGHSA enrichment
  62. 2026-06-13 03:07 UTCEG score recompute
  63. 2026-06-13 03:07 UTCGHSA enrichment
  64. 2026-06-12 23:12 UTCEPSS rescore
  65. 2026-06-12 23:12 UTCEPSS rescore
  66. 2026-06-12 15:00 UTCEG score recompute
  67. 2026-06-12 15:00 UTCGHSA enrichment
  68. 2026-06-12 02:55 UTCEG score recompute
  69. 2026-06-12 02:55 UTCGHSA enrichment
  70. 2026-06-11 14:50 UTCEG score recompute
  71. 2026-06-11 14:50 UTCGHSA enrichment
  72. 2026-06-11 14:00 UTCEPSS rescore
  73. 2026-06-11 02:45 UTCEG score recompute
  74. 2026-06-11 02:45 UTCGHSA enrichment
  75. 2026-06-10 22:18 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoC0xCyberstan/CVE-2026-46215-POC
    First seen Jun 18, 2026
    Open source ↗

Frequently asked(5)

What is CVE-2026-46215?
CVE-2026-46215 is a high vulnerability published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: drm: Set old handle to NULL before prime swap in change_handle There was a potential race condition in change_handle. The ioctl briefly had a single object with two idr entries; a concurrent gem_close could delete the object and…
When was CVE-2026-46215 disclosed?
CVE-2026-46215 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46215 actively exploited?
CVE-2026-46215 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46215?
CVE-2026-46215 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-46215?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46215, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-46215

Explore →

Is Your Infrastructure Affected by CVE-2026-46215?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.