CVE-2026-52976

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM 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
Trending — 4 sources updated this week
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: None knownExposed: 0

A fix is available — apply it.

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

drm/xe: Fix error cleanup in xe_exec_queue_create_ioctl()

Two error handling issues exist in xe_exec_queue_create_ioctl():

  • When xe_hw_engine_group_add_exec_queue() fails, the error path jumps
to put_exec_queue which skips xe_exec_queue_kill(). If the VM is in preempt fence mode, xe_vm_add_compute_exec_queue() has already added the queue to the VM's compute exec queue list. Skipping the kill leaves the queue on that list, leading to a dangling pointer after the queue is freed.
  • When xa_alloc() fails after xe_hw_engine_group_add_exec_queue() has
succeeded, the error path does not call xe_hw_engine_group_del_exec_queue() to remove the queue from the hw engine group list. The queue is then freed while still linked into the hw engine group, causing a use-after-free.

Fix both by:

  • Changing the xe_hw_engine_group_add_exec_queue() failure path to jump
to kill_exec_queue so that xe_exec_queue_kill() properly removes the queue from the VM's compute list.
  • Adding a del_hw_engine_group label before kill_exec_queue for the
xa_alloc() failure path, which removes the queue from the hw engine group before proceeding with the rest of the cleanup.

(cherry picked from commit 37c831f401746a45d510b312b0ed7a77b1e06ec8)

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

June 24, 2026

Last Modified

August 10, 2026

Advisory Details (4)

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

drm/xe: Fix error cleanup in xe_exec_queue_create_ioctl() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f93b00161213a0fe9f7ff1d8498ee5ca9e0a5c43
generic

drm/xe: Fix error cleanup in xe_exec_queue_create_ioctl() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f3cc22d4df3ed58439ea7e21daa54c3608e03b78
generic

drm/xe: Fix error cleanup in xe_exec_queue_create_ioctl() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/753b149d5a433eb19e0c1b0eb4526a6e26120d1f
generic

drm/xe: Fix error cleanup in xe_exec_queue_create_ioctl() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1be55646d8a2035343b012dcb12210db7bb8b056

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (137 versions)7.0.10-1

Weakness Classification(2)

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

Additional Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 35× in last 7d / 150× 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 222 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-52976?
CVE-2026-52976 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/xe: Fix error cleanup in xeexecqueuecreateioctl() Two error handling issues exist in xeexecqueuecreateioctl(): 1. When xehwenginegroupaddexecqueue() fails, the error path jumps to putexecqueue which skips xeexecqueue_kill(). If…
When was CVE-2026-52976 disclosed?
CVE-2026-52976 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on August 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-52976 actively exploited?
CVE-2026-52976 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 95.9% of all scored CVEs.
What is the CVSS score of CVE-2026-52976?
CVE-2026-52976 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-52976?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52976, 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-52976

Explore →

Is Your Infrastructure Affected by CVE-2026-52976?

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