Answer in brief
CVE-2025-39740 records a Unknown severity vulnerability in drm/xe/migrate: prevent potential UAF. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=270172f64b114451876c1b68912653e72ab99f38 <7e46fa64a4b94208563c3a5bf1d7f4346f94abea || >=270172f64b114451876c1b68912653e72ab99f38 <145832fbdd17b1d77ffd6cdd1642259e101d1b7e | 7e46fa64a4b94208563c3a5bf1d7f4346f94abea, 145832fbdd17b1d77ffd6cdd1642259e101d1b7e |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
Sep 11, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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)
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-39740 records a Unknown severity vulnerability in drm/xe/migrate: prevent potential UAF. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=270172f64b114451876c1b68912653e72ab99f38 <7e46fa64a4b94208563c3a5bf1d7f4346f94abea || >=270172f64b114451876c1b68912653e72ab99f38 <145832fbdd17b1d77ffd6cdd1642259e101d1b7e | 7e46fa64a4b94208563c3a5bf1d7f4346f94abea, 145832fbdd17b1d77ffd6cdd1642259e101d1b7e |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
Sep 11, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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)
Quoted source text, attributed separately from HOL analysis.