LiveActive security incident?Get immediate response
CVE Record

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

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.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A memory-lifetime error in Linux’s Intel Xe graphics driver can leave an exported synchronization fence pointing to freed data after its submit queue closes. A local low-privileged process could potentially trigger memory corruption affecting confidentiality, integrity, and availability. The supplied CVSS score is 7.8.

Executive priority

Prioritize remediation for multi-user endpoints, workstations, and compute hosts using the affected Xe driver. Schedule prompt kernel updates, but avoid declaring an emergency solely from this bundle because exploitation has not been reported and exposure requires local access.

Technical view

The drm/xe driver could free timeline names or shared-lock structures while exported dma-fences still referenced them, creating a use-after-free. The fix delays reclamation through RCU: queues use kfree_rcu, and per-GT shared-lock structures receive an RCU grace period before release.

Likely exposure

Exposure is limited to Linux systems running an affected kernel where the drm/xe driver is applicable and local users or processes can interact with submit queues and exported fences. The supplied version data identifies affected releases but does not clearly establish every distribution package or backport status.

Exploitation context

The CVSS vector describes local, low-complexity exploitation requiring low privileges and no user interaction. The source bundle does not report CISA KEV listing, public exploitation, or observed attacks. Treat exploitation status as unconfirmed rather than active.

Researcher notes

The defect is a dma-fence lifetime-rule violation involving data reachable after fence signaling. RCU-delayed reclamation addresses timeline-name and shared-lock lifetimes. No CWE is supplied. Exact vulnerable and fixed distribution builds require vendor confirmation because the bundled version list and repeated commit identifiers are insufficient for package-level conclusions.

Mitigation direction

  • Install a vendor-supported kernel containing the applicable referenced stable fix.
  • Check distribution advisories and package changelogs for CVE-2025-38703 backport status.
  • Restrict unnecessary local access until affected systems are updated.
  • Prioritize shared or multi-user systems using the Xe graphics driver.

Validation and detection

  • Inventory kernel versions on systems using Intel Xe graphics.
  • Determine whether the drm/xe driver is present and active.
  • Compare kernel package changelogs with the four referenced fix commits.
  • Confirm updated kernels are running after maintenance.
  • Regression-test fence export and queue closure in an isolated environment.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-38703 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-38703Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxdd08ebf6c3525a7ea2186e636df064ea47281987, dd08ebf6c3525a7ea2186e636df064ea47281987, dd08ebf6c3525a7ea2186e636df064ea47281987, dd08ebf6c3525a7ea2186e636df064ea47281987unaffected
LinuxLinux6.8, 0, 6.12.43, 6.15.11, 6.16.2, 6.17affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.