CVE-2026-52950

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
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/xe/dma-buf: fix UAF with retry loop

Retry doesn't work here, since bo will be freed on error, leading to UAF. However, now that we do the alloc & init before the attach, we can now combine this as one unit and have the init do the alloc for us. This should make the retry safe.

Reported by Sashiko.

v2: Fix up the error unwind (CI)

(cherry picked from commit 479669418253e0f27f8cf5db01a731352ea592e7)

CVSS v3
7.8
EG Score
7.8(high)
EPSS
3.7%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 22, 2026

Advisory Details (3)

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

drm/xe/dma-buf: fix UAF with retry loop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/827062952ed9bdf4220466c1f05ce452d04bdedf
generic

drm/xe/dma-buf: fix UAF with retry loop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/39fdac6be02eb7c3460518c1c4085f75f935c4ce
generic

drm/xe/dma-buf: fix UAF with retry loop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/155a372a1cc50fa93387c5d3cdfd614a61e1afd1

Vendor Advisories for CVE-2026-52950(2)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 73× 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.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-17 03:42 UTCGHSA enrichment
  9. 2026-07-16 17:03 UTCEPSS rescore
  10. 2026-07-16 16:24 UTCGHSA enrichment
  11. 2026-07-16 04:55 UTCGHSA enrichment
  12. 2026-07-15 17:40 UTCGHSA enrichment
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 16:57 UTCEPSS rescore
  15. 2026-07-15 06:12 UTCGHSA enrichment
  16. 2026-07-14 18:42 UTCGHSA enrichment
  17. 2026-07-14 07:25 UTCGHSA enrichment
  18. 2026-07-13 22:31 UTCEPSS rescore
  19. 2026-07-13 20:09 UTCGHSA enrichment
  20. 2026-07-13 08:54 UTCGHSA enrichment
  21. 2026-07-13 06:13 UTCEPSS rescore
  22. 2026-07-13 06:13 UTCEPSS rescore
  23. 2026-07-12 21:33 UTCGHSA enrichment
  24. 2026-07-12 10:18 UTCGHSA enrichment
  25. 2026-07-12 05:46 UTCEPSS rescore
Show 48 more
  1. 2026-07-11 23:02 UTCGHSA enrichment
  2. 2026-07-11 11:47 UTCGHSA enrichment
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-11 08:27 UTCEPSS rescore
  5. 2026-07-11 00:31 UTCGHSA enrichment
  6. 2026-07-10 13:16 UTCGHSA enrichment
  7. 2026-07-10 02:01 UTCGHSA enrichment
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-09 19:10 UTCEPSS rescore
  10. 2026-07-09 14:45 UTCGHSA enrichment
  11. 2026-07-09 03:27 UTCGHSA enrichment
  12. 2026-07-08 16:12 UTCGHSA enrichment
  13. 2026-07-08 15:16 UTCEPSS rescore
  14. 2026-07-08 15:16 UTCEPSS rescore
  15. 2026-07-08 04:57 UTCGHSA enrichment
  16. 2026-07-07 16:56 UTCGHSA enrichment
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-07 13:46 UTCEPSS rescore
  19. 2026-07-07 04:00 UTCGHSA enrichment
  20. 2026-07-06 16:30 UTCGHSA enrichment
  21. 2026-07-06 05:14 UTCGHSA enrichment
  22. 2026-07-06 02:23 UTCEPSS rescore
  23. 2026-07-06 02:23 UTCEPSS rescore
  24. 2026-07-05 17:57 UTCGHSA enrichment
  25. 2026-07-05 06:41 UTCGHSA enrichment
  26. 2026-07-04 19:24 UTCGHSA enrichment
  27. 2026-07-04 08:10 UTCGHSA enrichment
  28. 2026-07-04 06:31 UTCEPSS rescore
  29. 2026-07-03 20:49 UTCGHSA enrichment
  30. 2026-07-03 09:35 UTCGHSA enrichment
  31. 2026-07-02 22:19 UTCGHSA enrichment
  32. 2026-07-02 11:04 UTCGHSA enrichment
  33. 2026-07-01 23:47 UTCGHSA enrichment
  34. 2026-07-01 12:32 UTCGHSA enrichment
  35. 2026-07-01 01:17 UTCEG score recompute 7.80
  36. 2026-07-01 01:17 UTCGHSA enrichment
  37. 2026-06-30 23:22 UTCEPSS rescore
  38. 2026-06-29 14:06 UTCEPSS rescore
  39. 2026-06-29 14:06 UTCEPSS rescore
  40. 2026-06-28 14:07 UTCEPSS rescore
  41. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  42. 2026-06-28 04:56 UTCEPSS rescore
  43. 2026-06-28 04:56 UTCEPSS rescore
  44. 2026-06-27 21:54 UTCGHSA enrichment
  45. 2026-06-27 03:08 UTCEPSS rescore
  46. 2026-06-25 13:49 UTCEPSS rescore
  47. 2026-06-24 18:30 UTCEG score recompute
  48. 2026-06-24 18:02 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-52950?
CVE-2026-52950 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/xe/dma-buf: fix UAF with retry loop Retry doesn't work here, since bo will be freed on error, leading to UAF. However, now that we do the alloc & init before the attach, we can now combine this as one unit and have the init do…
When was CVE-2026-52950 disclosed?
CVE-2026-52950 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52950 actively exploited?
CVE-2026-52950 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-52950?
CVE-2026-52950 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-52950?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52950, 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-52950

Explore →

Is Your Infrastructure Affected by CVE-2026-52950?

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