CVE-2026-68384 (GCVE-0-2026-68384)

Vulnerability from cvelistv5 – Published: 2026-08-10 12:04 – Updated: 2026-08-17 05:04
VLAI
Title
drm/xe/vf: Fix VF CCS attach/detach race with in-flight BO moves
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/xe/vf: Fix VF CCS attach/detach race with in-flight BO moves xe_bo_move() attaches VF CCS read/write batch buffers (BBs) to a BO after it transitions NULL/SYSTEM -> TT, and detaches them after it transitions TT -> SYSTEM. Both operations were done synchronously on the CPU immediately after building the move's copy/clear fence, without waiting for that fence to signal. This creates two races with VF migration: - Attach happens too late relative to the copy job it is meant to protect. If the copy job is submitted before the CCS BBs are attached, a VF migration event that pauses execution mid-copy can observe partially copied CCS metadata without the attach state needed to correctly save/restore it. - Detach happens too early relative to the copy job that moves data out of TT. The CCS BBs are torn down right after the copy fence is obtained, while the actual blit may still be in flight. A VF migration event that pauses execution mid-copy can then race the save/restore path against the still-running blit, and the CCS BBs it would need to make sense of the paused state have already been removed. Fix both races: - Move the attach call to before the copy/clear job is submitted, so the CCS BBs are already registered by the time the copy runs. On attach failure, unwind and bail out of the move. xe_migrate_ccs_rw_copy() now takes the destination resource explicitly, since bo->ttm.resource is not updated to the new resource until after the move commits. - Detach only after explicitly waiting for the copy fence to signal, instead of tearing down the CCS BBs immediately after obtaining it. While here, also fix xe_sriov_vf_ccs_attach_bo() to properly unwind and propagate errors: the per-context loop previously never broke out on error, silently discarding earlier failures. Unwind by clearing each attached context directly via xe_migrate_ccs_rw_copy_clear() instead of reusing xe_sriov_vf_ccs_detach_bo(), which requires both contexts to be attached before it will clean up either one. (cherry picked from commit d45ad0aa7a1eb5d7288b5ed948b05695611dc39e)
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: 864690cf4dd62482b6dd049d82c509886c904303 , < 35ba43b541117bfb595e4b807ba447cf4335cc7d (git)
Affected: 864690cf4dd62482b6dd049d82c509886c904303 , < f2ebfd5cc87f1393a30c8b8b0a6c20cb22cffa97 (git)
Affected: 864690cf4dd62482b6dd049d82c509886c904303 , < 56441f9e08ad68697295b8835266d2bc48ab59b5 (git)
guessed Create a notification for this product.
Linux Linux Affected: 6.18
Unaffected: 0 , < 6.18 (semver)
Unaffected: 6.18.42 , ≤ 6.18.* (semver)
Unaffected: 7.1.6 , ≤ 7.1.* (semver)
Unaffected: 7.2 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/xe/xe_bo.c",
            "drivers/gpu/drm/xe/xe_migrate.c",
            "drivers/gpu/drm/xe/xe_migrate.h",
            "drivers/gpu/drm/xe/xe_sriov_vf_ccs.c",
            "drivers/gpu/drm/xe/xe_sriov_vf_ccs.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "35ba43b541117bfb595e4b807ba447cf4335cc7d",
              "status": "affected",
              "version": "864690cf4dd62482b6dd049d82c509886c904303",
              "versionType": "git"
            },
            {
              "lessThan": "f2ebfd5cc87f1393a30c8b8b0a6c20cb22cffa97",
              "status": "affected",
              "version": "864690cf4dd62482b6dd049d82c509886c904303",
              "versionType": "git"
            },
            {
              "lessThan": "56441f9e08ad68697295b8835266d2bc48ab59b5",
              "status": "affected",
              "version": "864690cf4dd62482b6dd049d82c509886c904303",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/xe/xe_bo.c",
            "drivers/gpu/drm/xe/xe_migrate.c",
            "drivers/gpu/drm/xe/xe_migrate.h",
            "drivers/gpu/drm/xe/xe_sriov_vf_ccs.c",
            "drivers/gpu/drm/xe/xe_sriov_vf_ccs.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.18"
            },
            {
              "lessThan": "6.18",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.42",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.1.*",
              "status": "unaffected",
              "version": "7.1.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.2",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.42",
                  "versionStartIncluding": "6.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1.6",
                  "versionStartIncluding": "6.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2",
                  "versionStartIncluding": "6.18",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "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\u0027s 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)"
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The affected code is reached through DRM/TTM buffer-object migration in the xe driver, driven by local ioctls on a render node (BO create/exec/eviction pressure). No network or remote input reaches xe_bo_move(), so local access to the GPU device node is required.\nAC:L - A local user can continuously drive TT\u003c-\u003eSYSTEM BO moves, keeping copy blits in flight indefinitely and making the attach/detach window essentially always open when a VF migration occurs, so the race is reliably winnable from the attacker\u0027s side.\nPR:L - Only an unprivileged local account with access to /dev/dri/renderD* is needed - render nodes are routinely accessible to normal users, graphical sessions and containers, and no capability check guards xe_bo_move() or the CCS attach/detach paths.\nUI:N - The attacker only needs to generate ordinary GPU buffer-object traffic; no victim action, file open, or mount is required, and VF migration is a routine automated hypervisor operation rather than a user-initiated one.\nS:U - The corrupted CCS batch buffers, pool nodes and metadata all belong to the guest VF kernel\u0027s own security authority; nothing crosses the VF/PF or IOMMU boundary.\nC:H - Detaching frees the sub-allocated CCS batch-buffer node back into the shared pool while the blit and the migration save/restore path may still use it, so recycled command buffers and stale PTEs can cause CCS metadata to be read from or copied out of unrelated buffer objects, exposing other users\u0027 GPU buffer contents.\nI:H - A freed-and-reused batch buffer executed by the GPU, plus attach state built against the wrong (old) resource, gives an attacker-influenceable write of CCS/compression metadata into memory that no longer belongs to the BO, corrupting other buffer objects and kernel-managed pool state.\nA:H - Executing torn-down or half-initialized batch buffers corrupts the migration blit and typically ends in a GPU engine hang/reset or failed VF migration, and the unwound-attach bug leaves inconsistent bb_ccs state that trips xe_assert() and leaks pool nodes until the device is unusable."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-17T05:04:30.813Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/35ba43b541117bfb595e4b807ba447cf4335cc7d"
        },
        {
          "url": "https://git.kernel.org/stable/c/f2ebfd5cc87f1393a30c8b8b0a6c20cb22cffa97"
        },
        {
          "url": "https://git.kernel.org/stable/c/56441f9e08ad68697295b8835266d2bc48ab59b5"
        }
      ],
      "title": "drm/xe/vf: Fix VF CCS attach/detach race with in-flight BO moves",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-68384",
    "datePublished": "2026-08-10T12:04:03.240Z",
    "dateReserved": "2026-07-30T09:28:09.387Z",
    "dateUpdated": "2026-08-17T05:04:30.813Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-68384",
      "date": "2026-08-20",
      "epss": "0.00134",
      "percentile": "0.0337"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-68384\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-08-10T13:20:31.593\",\"lastModified\":\"2026-08-17T06:17:46.920\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"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\u0027s 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)\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"drivers/gpu/drm/xe/xe_bo.c\",\"drivers/gpu/drm/xe/xe_migrate.c\",\"drivers/gpu/drm/xe/xe_migrate.h\",\"drivers/gpu/drm/xe/xe_sriov_vf_ccs.c\",\"drivers/gpu/drm/xe/xe_sriov_vf_ccs.h\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"864690cf4dd62482b6dd049d82c509886c904303\",\"lessThan\":\"35ba43b541117bfb595e4b807ba447cf4335cc7d\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"864690cf4dd62482b6dd049d82c509886c904303\",\"lessThan\":\"f2ebfd5cc87f1393a30c8b8b0a6c20cb22cffa97\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"864690cf4dd62482b6dd049d82c509886c904303\",\"lessThan\":\"56441f9e08ad68697295b8835266d2bc48ab59b5\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"drivers/gpu/drm/xe/xe_bo.c\",\"drivers/gpu/drm/xe/xe_migrate.c\",\"drivers/gpu/drm/xe/xe_migrate.h\",\"drivers/gpu/drm/xe/xe_sriov_vf_ccs.c\",\"drivers/gpu/drm/xe/xe_sriov_vf_ccs.h\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"6.18\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"6.18\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.18.42\",\"lessThanOrEqual\":\"6.18.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"7.1.6\",\"lessThanOrEqual\":\"7.1.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"7.2\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\",\"baseScore\":7.8,\"baseSeverity\":\"HIGH\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":5.9}]},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/35ba43b541117bfb595e4b807ba447cf4335cc7d\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/56441f9e08ad68697295b8835266d2bc48ab59b5\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/f2ebfd5cc87f1393a30c8b8b0a6c20cb22cffa97\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}",
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-08-14T05:59:39+00:00",
      "cve": "CVE-2026-68384",
      "id": "CVE-2026-68384",
      "initial_release_date": "2026-08-10T00:00:00+00:00",
      "product_status:known_affected": "184",
      "product_status:known_not_affected": "92",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: drm/xe/vf: Fix VF CCS attach/detach race with in-flight BO moves",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-68384.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-08-13T01:28:04Z",
      "cve": "CVE-2026-68384",
      "id": "CVE-2026-68384",
      "initial_release_date": "2026-08-12T16:22:23Z",
      "product_status:known_not_affected": "296",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2026-68384",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2026-68384.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…