CVE-2026-52976

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
Trending — 3 sources updated this week
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: 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(high)
EPSS
2.8%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 30, 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

Vendor Advisories for CVE-2026-52976(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 34× in last 7d / 46× 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-06 23:55 UTCEG score recompute
  2. 2026-07-06 23:55 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 11:21 UTCEG score recompute
  6. 2026-07-06 11:21 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 22:46 UTCEG score recompute
  10. 2026-07-05 22:46 UTCGHSA enrichment
  11. 2026-07-05 10:12 UTCEG score recompute
  12. 2026-07-05 10:12 UTCGHSA enrichment
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 21:38 UTCEG score recompute
  16. 2026-07-04 21:38 UTCGHSA enrichment
  17. 2026-07-04 09:05 UTCEG score recompute
  18. 2026-07-04 09:05 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-03 20:30 UTCEG score recompute
  21. 2026-07-03 20:30 UTCGHSA enrichment
  22. 2026-07-03 07:56 UTCEG score recompute
  23. 2026-07-03 07:56 UTCGHSA enrichment
  24. 2026-07-02 19:22 UTCEG score recompute
  25. 2026-07-02 19:22 UTCGHSA enrichment
Show 21 more
  1. 2026-07-02 06:48 UTCEG score recompute
  2. 2026-07-02 06:47 UTCGHSA enrichment
  3. 2026-07-01 18:13 UTCEG score recompute
  4. 2026-07-01 18:13 UTCGHSA enrichment
  5. 2026-07-01 05:38 UTCEG score recompute
  6. 2026-07-01 05:38 UTCGHSA enrichment
  7. 2026-06-30 23:22 UTCEPSS rescore
  8. 2026-06-30 17:02 UTCEG score recompute 7.80
  9. 2026-06-30 17:02 UTCGHSA enrichment
  10. 2026-06-29 14:06 UTCEPSS rescore
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-28 14:07 UTCEPSS rescore
  13. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  14. 2026-06-28 04:56 UTCEPSS rescore
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-27 17:43 UTCEG score recompute
  17. 2026-06-27 17:43 UTCGHSA enrichment
  18. 2026-06-27 03:08 UTCEPSS rescore
  19. 2026-06-25 13:49 UTCEPSS rescore
  20. 2026-06-24 18:27 UTCEG score recompute
  21. 2026-06-24 18:02 UTCNVD updatefirst tracked

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 June 30, 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 2.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.