In the Linux kernel, the following vulnerability has been resolved:
drm/xe/migrate: prevent potential UAF
If we hit the error path, the previous fence (if there is one) has
already been put() prior to this, so doing a fence_wait could lead to
UAF. Tweak the flow to do to the put() until after we do the wait.
(cherry picked from commit 9b7ca35ed28fe5fad86e9d9c24ebd1271e4c9c3e)
Security readout for executives and security teams
Plain-English summary
A Linux graphics-driver error path can use a synchronization object after it has been released. This may let a locally authenticated, low-privileged user compromise confidentiality, integrity, or availability on affected systems. Successful exploitation conditions and practical impact are not documented in the supplied sources.
Executive priority
Treat as a high-priority local privilege-boundary risk on affected Linux endpoints and shared compute systems. Accelerate patching where untrusted users or workloads have local access. Internet-facing status alone does not increase direct exposure because the supplied vector is local.
Technical view
The drm/xe migration error path releases a previous fence before waiting on it, creating a potential use-after-free. The upstream correction moves the fence release until after the wait. CVSS 3.1 is 7.8: local access, low complexity, low privileges, no user interaction, and potentially high impact across confidentiality, integrity, and availability.
Likely exposure
Exposure is limited to Linux systems running affected kernel code in the drm/xe migration subsystem. The supplied version representation is ambiguous, so confirm the exact kernel build and whether it contains the relevant stable fix. Remote-only services are not directly exposed under the supplied local-attack vector.
Exploitation context
The supplied record does not show CISA KEV inclusion or cite active exploitation, public proof-of-concept code, or weaponization. Exploitation requires local access with low privileges according to CVSS. Trigger reliability and required hardware, configuration, or workload conditions are not established by the sources.
Researcher notes
The defect concerns fence lifetime ordering on an error path: put occurs before fence_wait, permitting a potential stale reference. Two stable-kernel commits are cited, likely reflecting branch-specific backports. The bundle does not establish reachability prerequisites, exploitability, affected hardware, or precise fixed-version boundaries; validate against source history and distribution advisories.
Mitigation direction
Apply a vendor-supported kernel update containing the appropriate referenced stable fix.
Consult the Linux distribution advisory for exact fixed package versions.
Prioritize shared systems where untrusted users can execute local workloads.
Restrict local account and workload access until remediation is confirmed.
Validation and detection
Record the running kernel and distribution package versions.
Determine whether the system uses the drm/xe driver and relevant migration functionality.
Check whether the applicable stable fix commit is included in the kernel build.
Review kernel logs for graphics migration errors or unexplained crashes.
Revalidate after updating by confirming the running kernel contains the fix.
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-39740 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
3Source 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.