CVE-2026-68382: drm/xe/guc: Hold device ref until queue teardown completes

Published Aug 10, 2026
·
Updated

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 drmdevice 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, gucsubmitswfini() cannot run with live GuC IDs. Replace the fini wait with an assertion and remove the unused finiwq.

v2: - Rebase

v3: - Switch to queue-lifetime drmdevget()/drmdevput() model. (Matt) - Queue async teardown on systemdflwq instead of xe->destroywq. (Matt) - Drop separate deferred drmdevput worker. - Remove stale drainworkqueue(xe->destroywq) from gucsubmitswfini().

v4: - Replace the gucsubmitswfini() wait with an assertion and remove the now-unused finiwq. (sashiko)

v5: - Move destroy work to a module-lifetime Xe workqueue instead of systemdflwq. (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 destroywq to avoid letting it outlive the xedevice/drmdevice. (Sashiko) - Use WQMEMRECLAIM for xe->destroywq because SVM pagemap destroy work can be queued from the reclaim path.

v7: - Drop the per-device xe->destroywq and use the module-level destroy WQ for SVM pagemap destroy as well. (Matt) - Rename xeexecqueuedestroywq() helpers to xedestroywq() helpers because the WQ is no longer exec-queue specific. (Matt)

v8: - Rebase.

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

v10: - Keep xe->destroywq per-cpu while adding WQMEMRECLAIM 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 Software

1 affected component
Linux Kernel

Event History

Aug 10, 2026
CVE Published
via MITRE·12:04 PM
Data Sourced
via MITRE·12:04 PM
Description
Data Sourced
via NVD·01:20 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-68382?

CVE-2026-68382 has a risk score of 28 which indicates a significant level of risk.

2

How do I fix CVE-2026-68382?

To fix CVE-2026-68382, update to the latest version of the Linux kernel where the issue has been resolved.

3

What systems are affected by CVE-2026-68382?

CVE-2026-68382 affects systems running the Linux kernel that use the drm/xe/guc subsystem.

4

What does CVE-2026-68382 involve?

CVE-2026-68382 involves a potential deadlock scenario during the teardown of the GuC exec queue in the Linux kernel.

5

When was CVE-2026-68382 published?

CVE-2026-68382 was published on August 10, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203