CVE-2026-68382

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-10. 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.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

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/guc: Hold device ref until queue teardown completes

GuC exec queue destruction can run asynchronously. If the final device put happens from a destroy worker, drmm cleanup can end up draining the same workqueue and deadlock.

Hold a drm_device reference for the queue lifetime and drop it after queue teardown completes. This keeps drmm cleanup from running while async destroy work is still pending.

Move GuC destroy work to a module-lifetime Xe workqueue and flush it on PCI remove so hot-unbind/rebind still waits for pending destroy work.

With queue-held device refs, guc_submit_sw_fini() cannot run with live GuC IDs. Replace the fini wait with an assertion and remove the unused fini_wq.

v2:

  • Rebase

v3:

  • Switch to queue-lifetime drm_dev_get()/drm_dev_put() model. (Matt)
  • Queue async teardown on system_dfl_wq instead of xe->destroy_wq. (Matt)
  • Drop separate deferred drm_dev_put worker.
  • Remove stale drain_workqueue(xe->destroy_wq) from guc_submit_sw_fini().

v4:

  • Replace the guc_submit_sw_fini() wait with an assertion and remove
the now-unused fini_wq. (sashiko)

v5:

  • Move destroy work to a module-lifetime Xe workqueue instead of
system_dfl_wq. (Matt)
  • Flush the module-lifetime destroy workqueue during PCI remove to
preserve the old device-remove wait semantics.

v6:

  • Keep SVM pagemap destroy work on the per-device destroy_wq to avoid
letting it outlive the xe_device/drm_device. (Sashiko)
  • Use WQ_MEM_RECLAIM for xe->destroy_wq because SVM pagemap destroy work
can be queued from the reclaim path.

v7:

  • Drop the per-device xe->destroy_wq and use the module-level destroy WQ
for SVM pagemap destroy as well. (Matt)
  • Rename xe_exec_queue_destroy_wq_*() helpers to xe_destroy_wq_*()
helpers because the WQ is no longer exec-queue specific. (Matt)

v8:

  • Rebase.

v9:

  • Keep SVM pagemap destroy work on the per-device WQ_MEM_RECLAIM
destroy_wq because it can be queued from reclaim and embeds the dev_pagemap used by devres teardown. (Sashiko)
  • Keep the module-level destroy WQ GuC-only and drop WQ_MEM_RECLAIM
from it.
  • Update the module-WQ kdoc to document the GuC/SVM split.

v10:

  • Keep xe->destroy_wq per-cpu while adding WQ_MEM_RECLAIM to fix the
workqueue allocation warning.

v11:

  • Drop the SVM pagemap destroy comment as it was revision-specific.
(Thomas)

v12:

  • Rebase.

(cherry picked from commit da1124abac689cc2b1d8995e5f0a816f8a122edb)

CVSS v3
7.8
EG Score
7.8(high)
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
3%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 17, 2026

Advisory Details (2)

Auto-updated Aug 14, 2026
No patch confirmed yet.
generic

drm/xe/guc: Hold device ref until queue teardown completes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9b7e60184f4b22e893d4ae95234d5f26261a430c
generic

drm/xe/guc: Hold device ref until queue teardown completes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/03d6f83979b0d75a0b0893dfe1735ec93facf515

Vendor Advisories for CVE-2026-68382(1)

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

Data Freshness Timeline

(refreshed 31× in last 7d / 43× 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-08-21 08:47 UTCGHSA enrichment
  2. 2026-08-20 20:35 UTCGHSA enrichment
  3. 2026-08-20 08:23 UTCGHSA enrichment
  4. 2026-08-19 20:12 UTCEG score recompute
  5. 2026-08-19 20:12 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 07:57 UTCGHSA enrichment
  8. 2026-08-18 19:45 UTCEG score recompute
  9. 2026-08-18 19:45 UTCGHSA enrichment
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 07:32 UTCGHSA enrichment
  13. 2026-08-17 19:19 UTCEG score recompute
  14. 2026-08-17 19:19 UTCGHSA enrichment
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 06:32 UTCEG score recompute
  17. 2026-08-17 06:31 UTCGHSA enrichment
  18. 2026-08-17 05:36 UTCEG score recompute
  19. 2026-08-17 05:36 UTCGHSA enrichment
  20. 2026-08-17 00:55 UTCEG score recompute
  21. 2026-08-17 00:55 UTCGHSA enrichment
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 12:43 UTCEG score recompute
  24. 2026-08-16 12:43 UTCGHSA enrichment
  25. 2026-08-16 00:31 UTCGHSA enrichment
Show 18 more
  1. 2026-08-15 12:19 UTCEG score recompute
  2. 2026-08-15 12:19 UTCGHSA enrichment
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-15 00:07 UTCGHSA enrichment
  5. 2026-08-14 11:55 UTCEG score recompute
  6. 2026-08-14 11:55 UTCGHSA enrichment
  7. 2026-08-13 23:44 UTCEG score recompute
  8. 2026-08-13 23:44 UTCGHSA enrichment
  9. 2026-08-13 23:03 UTCEG score recompute 7.80
  10. 2026-08-13 23:03 UTCGHSA enrichment
  11. 2026-08-13 23:03 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  12. 2026-08-13 22:00 UTCEPSS rescore
  13. 2026-08-13 16:39 UTCEG score recompute
  14. 2026-08-13 16:39 UTCGHSA enrichment
  15. 2026-08-12 13:51 UTCEPSS rescore
  16. 2026-08-10 13:24 UTCNVD update
  17. 2026-08-10 12:18 UTCEG score recompute
  18. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68382?
CVE-2026-68382 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/xe/guc: Hold device ref until queue teardown completes GuC exec queue destruction can run asynchronously. If the final device put happens from a destroy worker, drmm cleanup can end up draining the same workqueue and deadlock.…
When was CVE-2026-68382 disclosed?
CVE-2026-68382 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68382 actively exploited?
CVE-2026-68382 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 97.0% of all scored CVEs.
What is the CVSS score of CVE-2026-68382?
CVE-2026-68382 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68382?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68382, 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-68382

Explore →

Is Your Infrastructure Affected by CVE-2026-68382?

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