CVE-2026-68382

Device teardown hang via workqueue self-deadlock

Published Aug 10, 2026 · Updated Aug 10, 2026

Deadlock in the Xe GuC driver in affected Linux kernel releases allows attackers to hang device teardown during queue destruction. An asynchronous GuC queue-destroy worker can issue the final drm_device put, start drmm cleanup, and make cleanup drain the same workqueue that is executing it. The path requires an Intel Xe GuC execution queue and teardown or PCI removal while destroy work remains pending; published material does not identify attacker privileges or a broader system impact.

CVSS severityUnavailable
Unscored
EPSS probability0.13%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Deadlock in the Xe GuC driver in affected Linux kernel releases allows attackers to hang device teardown during queue destruction. An asynchronous GuC queue-destroy worker can issue the final drm_device put, start drmm cleanup, and make cleanup drain the same workqueue that is executing it. The path requires an Intel Xe GuC execution queue and teardown or PCI removal while destroy work remains pending; published material does not identify attacker privileges or a broader system impact.

The record

CVE
CVE-2026-68382
Published
Aug 10, 2026
Updated
Aug 10, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1499
Attack vector
Unavailable
Privileges
Unavailable

Timeline

How it unfolded

  1. Aug 10, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 10, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=272b0e78874586d6ccae04079d75b27b47705544
  2. Affected versionversion=2d2be279f1ca9e7288282d4214f16eea8a727cdb <03d6f83979b0d75a0b0893dfe1735ec93facf515
  3. Affected versionversion=2d2be279f1ca9e7288282d4214f16eea8a727cdb <9b7e60184f4b22e893d4ae95234d5f26261a430c
  4. Affected versionversion=421c74670b0f9d5c007f1276d3647aa58f407fde
  5. Affected versionversion=6.10.14 <6.11
  6. Affected versionversion=6.11.3 <6.12
  7. Affected versionversion=6.12

What conditions does exploitation require?

Attack vectorUnavailable in this record.
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=272b0e78874586d6ccae04079d75b27b47705544; version=2d2be279f1ca9e7288282d4214f16eea8a727cdb <03d6f83979b0d75a0b0893dfe1735ec93facf515; version=2d2be279f1ca9e7288282d4214f16eea8a727cdb <9b7e60184f4b22e893d4ae95234d5f26261a430c; version=421c74670b0f9d5c007f1276d3647aa58f407fde; version=6.10.14 <6.11; version=6.11.3 <6.12; version=6.12

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
VectorUnavailable
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo