Skip to content
Heist/ feed
Back to feed
HighFix available

drm/xe: Make dma-fences compliant with the safe access rules

Type: advisorySources: OSV

In the Linux kernel, the following vulnerability has been resolved: drm/xe: Make dma-fences compliant with the safe access rules Xe can free some of the data pointed to by the dma-fences it exports. Most notably the timeline name can get freed if userspace closes the associated submit queue. At the same time the fence could have been exported to a third party (for example a sync_fence fd) which will then cause an use- after-free on subsequent access. To make this safe we need to make the driver compliant with the newly documented dma-fence rules. Driver has to ensure a RCU grace period between signalling a fence and freeing any data pointed to by said fence. For the timeline name we simply make the queue be freed via kfree_rcu and for the shared lock associated with multiple queues we add a RCU grace period before freeing the per GT structure holding the lock.

Products
Kernel
Affected versions
Not specified
Fixed versions
6.12.43, 6.15.11, 6.16.2
CVEs
CVE-2025-38703
Confirmed fixed CVEs
Not specified
Updated in this feed
2 Nov 2026, 20:21 UTC · Revision 1

Source evidence

drm/xe: Make dma-fences compliant with the safe access rules

core-osv · Original source

Published 4 Sept 2025, 15:32 UTC

In the Linux kernel, the following vulnerability has been resolved: drm/xe: Make dma-fences compliant with the safe access rules Xe can free some of the data pointed to by the dma-fences it exports. Most notably the timeline name can get freed if userspace closes the associated submit queue. At the same time the fence could have been exported to a third party (for example a sync_fence fd) which will then cause an use- after-free on subsequent access. To make this safe we need to make the driver compliant with the newly documented dma-fence rules. Driver has to ensure a RCU grace period between signalling a fence and freeing any data pointed to by said fence. For the timeline name we simply make the queue be freed via kfree_rcu and for the shared lock associated with multiple queues we add a RCU grace period before freeing the per GT structure holding the lock.

osv:CVE-2025-38703

Kernel

Fixed versions: 6.12.43, 6.15.11, 6.16.2

Complete source record
{
  "id": "7707b245db4bf37bb7e8b41b246eedeee25ca039813b8c5f73d9095be57099da",
  "url": "https://osv.dev/vulnerability/CVE-2025-38703",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "drm/xe: Make dma-fences compliant with the safe access rules",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: drm/xe: Make dma-fences compliant with the safe access rules Xe can free some of the data pointed to by the dma-fences it exports. Most notably the timeline name can get freed if userspace closes the associated submit queue. At the same time the fence could have been exported to a third party (for example a sync_fence fd) which will then cause an use- after-free on subsequent access. To make this safe we need to make the driver compliant with the newly documented dma-fence rules. Driver has to ensure a RCU grace period between signalling a fence and freeing any data pointed to by said fence. For the timeline name we simply make the queue be freed via kfree_rcu and for the shared lock associated with multiple queues we add a RCU grace period before freeing the per GT structure holding the lock.",
    "evidence": "osv:CVE-2025-38703",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.12.43",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.15.11",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.16.2",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "high",
    "structured": {
      "id": "CVE-2025-38703",
      "aliases": [
        "CVE-2025-38703"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "dd08ebf6c3525a7ea2186e636df064ea47281987"
                },
                {
                  "fixed": "b17fcce70733c211cb5dabf54f4f9491920b1d92"
                },
                {
                  "fixed": "ba37807d08bae67de6139346a85650cab5f6145a"
                },
                {
                  "fixed": "683b0e397dad9f26a42dcacf6f7f545a77ce6c06"
                },
                {
                  "fixed": "6bd90e700b4285e6a7541e00f969cab0d696adde"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38703.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.8.0"
                },
                {
                  "fixed": "6.12.43"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.13.0"
                },
                {
                  "fixed": "6.15.11"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.16.0"
                },
                {
                  "fixed": "6.16.2"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38703.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:23.360046740Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/683b0e397dad9f26a42dcacf6f7f545a77ce6c06",
        "https://git.kernel.org/stable/c/6bd90e700b4285e6a7541e00f969cab0d696adde",
        "https://git.kernel.org/stable/c/b17fcce70733c211cb5dabf54f4f9491920b1d92",
        "https://git.kernel.org/stable/c/ba37807d08bae67de6139346a85650cab5f6145a",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38703.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2025-38703",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38703.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2025-38703",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 489790,
  "published_at": "2025-09-04T15:32:54.779+00:00"
}