{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68384 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68384 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-68384 and fix it if it is affected.\n\nWhat it is: CVE-2026-68384 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-68384 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-68384/ (Markdown: https://insights.sbomify.com/CVE-2026-68384/index.md)","id":"CVE-2026-68384","markdown":"https://insights.sbomify.com/CVE-2026-68384/index.md","name":"CVE-2026-68384","record":{"aliases":["BELL-CVE-2026-68384","DEBIAN-CVE-2026-68384","GHSA-hr8j-ghcq-qgrr","UBUNTU-CVE-2026-68384"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","data_modify"],"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 allows VF migration events to observe inconsistent CCS metadata, potentially leading to data corruption or exposure.","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/vf: Fix VF CCS attach/detach race with in-flight BO moves\n\nxe_bo_move() attaches VF CCS read/write batch buffers (BBs) to a BO\nafter it transitions NULL/SYSTEM -\u003e TT, and detaches them after it\ntransitions TT -\u003e SYSTEM. Both operations were done synchronously on\nthe CPU immediately after building the move's copy/clear fence,\nwithout waiting for that fence to signal. This creates two races with\nVF migration:\n\n- Attach happens too late relative to the copy job it is meant to\n  protect. If the copy job is submitted before the CCS BBs are\n  attached, a VF migration event that pauses execution mid-copy can\n  observe partially copied CCS metadata without the attach state\n  needed to correctly save/restore it.\n\n- Detach happens too early relative to the copy job that moves data\n  out of TT. The CCS BBs are torn down right after the copy fence is\n  obtained, while the actual blit may still be in flight. A VF\n  migration event that pauses execution mid-copy can then race the\n  save/restore path against the still-running blit, and the CCS BBs\n  it would need to make sense of the paused state have already been\n  removed.\n\nFix both races:\n\n- Move the attach call to before the copy/clear job is submitted, so\n  the CCS BBs are already registered by the time the copy runs. On\n  attach failure, unwind and bail out of the move. xe_migrate_ccs_rw_copy()\n  now takes the destination resource explicitly, since bo-\u003ettm.resource\n  is not updated to the new resource until after the move commits.\n\n- Detach only after explicitly waiting for the copy fence to signal,\n  instead of tearing down the CCS BBs immediately after obtaining it.\n\nWhile here, also fix xe_sriov_vf_ccs_attach_bo() to properly unwind and\npropagate errors: the per-context loop previously never broke out on\nerror, silently discarding earlier failures. Unwind by clearing each\nattached context directly via xe_migrate_ccs_rw_copy_clear() instead of\nreusing xe_sriov_vf_ccs_detach_bo(), which requires both contexts to be\nattached before it will clean up either one.\n\n(cherry picked from commit d45ad0aa7a1eb5d7288b5ed948b05695611dc39e)","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/vf: Fix VF CCS attach/detach race with in-flight BO moves","id":"CVE-2026-68384","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":"s390/checksum: Fix csum_partial() without vector facility","id":"CVE-2026-68385"},"packages":[],"prev":{"headline":"drm/xe/guc: Keep scheduler timeline name alive","id":"CVE-2026-68383"},"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 allows VF migration events to observe inconsistent CCS metadata, potentially leading to data corruption or exposure.","url":"https://insights.sbomify.com/CVE-2026-68384/"}