How severe is CVE-2026-68382?

No CVSS score has been assigned to CVE-2026-68382 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-68382?

CVE-2026-68382 affects the following packages: Kernel (Linux). Ecosystems affected: Linux.

How do I fix CVE-2026-68382?

Update Kernel to 7.1.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-68382 is resolved across your whole dependency graph.

How do I detect CVE-2026-68382 in my Linux dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Kernel. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2026-68382 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2026-68382?

O3 pinpoints whether CVE-2026-68382 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2026-68382 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-68382 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was CVE-2026-68382 published, and has it been updated?

CVE-2026-68382 was published on August 10, 2026 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐧 Linux

Not in CISA KEV

CVE-2026-68382

CVE-2026-68382 is a security vulnerability in Kernel. O3 Security confirms whether CVE-2026-68382 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

drm/xe/guc: Hold device ref until queue teardown completes

Published

Aug 10, 2026

Updated

Aug 12, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐧Kernel

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Linux packages — download data is not available via public APIs for these ecosystems.

Description

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)

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐧Linux	`Kernel`	≥ 6.12.0&&< 7.1.6	7.1.6

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Kernel. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update Kernel to 7.1.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-68382 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-68382 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2026-68382. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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 pe

O3 Security · Impact-Aware SCA

Is CVE-2026-68382 in your dependencies?

O3 detects CVE-2026-68382 across Linux dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works