{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68382 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68382 is a high-severity vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-68382 and fix it if it is affected.\n\nWhat it is: CVE-2026-68382 is a high-severity vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-68382 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-68382/ (Markdown: https://insights.sbomify.com/CVE-2026-68382/index.md)","id":"CVE-2026-68382","markdown":"https://insights.sbomify.com/CVE-2026-68382/index.md","name":"CVE-2026-68382","record":{"aliases":["BELL-CVE-2026-68382","DEBIAN-CVE-2026-68382","GHSA-j3x5-5jxr-fgc6","UBUNTU-CVE-2026-68382"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel's Xe GPU driver can cause a deadlock during queue teardown, leading to a denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/xe/guc: Hold device ref until queue teardown completes\n\nGuC exec queue destruction can run asynchronously. If the final device\nput happens from a destroy worker, drmm cleanup can end up draining\nthe same workqueue and deadlock.\n\nHold a drm_device reference for the queue lifetime and drop it after\nqueue teardown completes. This keeps drmm cleanup from running while\nasync destroy work is still pending.\n\nMove GuC destroy work to a module-lifetime Xe workqueue and flush it\non PCI remove so hot-unbind/rebind still waits for pending destroy work.\n\nWith queue-held device refs, guc_submit_sw_fini() cannot run with live\nGuC IDs. Replace the fini wait with an assertion and remove the unused\nfini_wq.\n\nv2:\n  - Rebase\n\nv3:\n  - Switch to queue-lifetime drm_dev_get()/drm_dev_put() model. (Matt)\n  - Queue async teardown on system_dfl_wq instead of xe-\u003edestroy_wq. (Matt)\n  - Drop separate deferred drm_dev_put worker.\n  - Remove stale drain_workqueue(xe-\u003edestroy_wq) from guc_submit_sw_fini().\n\nv4:\n  - Replace the guc_submit_sw_fini() wait with an assertion and remove\n    the now-unused fini_wq. (sashiko)\n\nv5:\n  - Move destroy work to a module-lifetime Xe workqueue instead of\n    system_dfl_wq. (Matt)\n  - Flush the module-lifetime destroy workqueue during PCI remove to\n    preserve the old device-remove wait semantics.\n\nv6:\n  - Keep SVM pagemap destroy work on the per-device destroy_wq to avoid\n    letting it outlive the xe_device/drm_device. (Sashiko)\n  - Use WQ_MEM_RECLAIM for xe-\u003edestroy_wq because SVM pagemap destroy work\n    can be queued from the reclaim path.\n\nv7:\n  - Drop the per-device xe-\u003edestroy_wq and use the module-level destroy WQ\n    for SVM pagemap destroy as well. (Matt)\n  - Rename xe_exec_queue_destroy_wq_*() helpers to xe_destroy_wq_*()\n    helpers because the WQ is no longer exec-queue specific. (Matt)\n\nv8:\n  - Rebase.\n\nv9:\n  - Keep SVM pagemap destroy work on the per-device WQ_MEM_RECLAIM\n    destroy_wq because it can be queued from reclaim and embeds\n    the dev_pagemap used by devres teardown. (Sashiko)\n  - Keep the module-level destroy WQ GuC-only and drop WQ_MEM_RECLAIM\n    from it.\n  - Update the module-WQ kdoc to document the GuC/SVM split.\n\nv10:\n  - Keep xe-\u003edestroy_wq per-cpu while adding WQ_MEM_RECLAIM to fix the\n    workqueue allocation warning.\n\nv11:\n  - Drop the SVM pagemap destroy comment as it was revision-specific.\n    (Thomas)\n\nv12:\n  - Rebase.\n\n(cherry picked from commit da1124abac689cc2b1d8995e5f0a816f8a122edb)","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"drm/xe/guc: Hold device ref until queue teardown completes","id":"CVE-2026-68382","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"drm/xe/guc: Keep scheduler timeline name alive","id":"CVE-2026-68383"},"packages":[],"prev":{"headline":"ksmbd: pin conn during async oplock break notification","id":"CVE-2026-68381"},"products":["Linux"],"published":"2026-08-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A race condition in the Linux kernel's Xe GPU driver can cause a deadlock during queue teardown, leading to a denial of service.","url":"https://insights.sbomify.com/CVE-2026-68382/"}