CVE-2026-46215

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-28. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Elevated
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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)
EG Risk
51(Track*)
EG Risk 51/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

May 28, 2026

Last Modified

August 5, 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

Patch Availability(10)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (135 versions)7.0.9-1

Weakness Classification(1)

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

Additional Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 4× in last 7d / 82× 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 253 total refreshes for this CVE.

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

Publicly available exploits

(3 references)

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

  • GitHub PoCbluedragonsecurity/CVE-2026-46215-exploit-linux-7.0-uaf-stable
    First seen Jul 19, 2026

    CVE-2026-46215 DRM GEM UAF Exploit for Linux 7.0 - by Antonius (sw0rdm4n, w1sdom, ev1lut10n)

    Open source ↗
  • GitHub PoCbluedragonsecurity/CVE-2026-46215-EXPLOIT
    First seen Jul 11, 2026

    This is an exploit for CVE-2026-46215 (Linux Kernel Use After Free) Adapted for Linux 7.0 !!! by Antonius (ev1lut10n / sw0rdm4n)

    Open source ↗
  • 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 August 5, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 86.6% of all scored CVEs.
What is the CVSS score of CVE-2026-46215?
CVE-2026-46215 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
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

See which npm, PyPI, Go, and Maven packages are affected by 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.