← All Advisories
Reported from OT-Advisories.com as of

Linux Kernel DRM graphics subsystem Vulnerability Rated 7.8 CVSS

Last refreshed2026-10-15

Status: UPDATED  |  Advisory ID: CVE-2026-68382

Key Details

CVECVE-2026-68382
CVSS Score / Version
7.8 (High) / CVSS v3.1
Updated2026-10-15
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS Prose
attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products
Linux Kernel
Exploitation prediction (EPSS)
0.13% probability of exploitation in the next 30 days (2% percentile) -- FIRST.org's EPSS model.

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

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) (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-68382
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-68382
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.