Answer in brief
CVE-2025-38511 records a Unknown severity vulnerability in drm/xe/pf: Clear all LMTT pages on alloc. 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 | >=b1d20405821812ad70d95eefe58cadc6d50b0917 <ff4b8c9ade1b82979fdd01e6f45b60f92eed26d8 || >=b1d20405821812ad70d95eefe58cadc6d50b0917 <5d21892c2e15b6a27f8bc907693eca7c6b7cc269 || >=b1d20405821812ad70d95eefe58cadc6d50b0917 <705a412a367f383430fa34bada387af2e52eb043 | ff4b8c9ade1b82979fdd01e6f45b60f92eed26d8, 5d21892c2e15b6a27f8bc907693eca7c6b7cc269, 705a412a367f383430fa34bada387af2e52eb043 |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Aug 16, 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/pf: Clear all LMTT pages on alloc Our LMEM buffer objects are not cleared by default on alloc and during VF provisioning we only setup LMTT PTEs for the actually provisioned LMEM range. But beyond that valid range we might leave some stale data that could either point to some other VFs allocations or even to the PF pages. Explicitly clear all new LMTT page to avoid the risk that a malicious VF would try to exploit that gap. While around add asserts to catch any undesired PTE overwrites and low-level debug traces to track LMTT PT life-cycle. (cherry picked from commit 3fae6918a3e27cce20ded2551f863fb05d4bef8d)
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-38511 records a Unknown severity vulnerability in drm/xe/pf: Clear all LMTT pages on alloc. 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 | >=b1d20405821812ad70d95eefe58cadc6d50b0917 <ff4b8c9ade1b82979fdd01e6f45b60f92eed26d8 || >=b1d20405821812ad70d95eefe58cadc6d50b0917 <5d21892c2e15b6a27f8bc907693eca7c6b7cc269 || >=b1d20405821812ad70d95eefe58cadc6d50b0917 <705a412a367f383430fa34bada387af2e52eb043 | ff4b8c9ade1b82979fdd01e6f45b60f92eed26d8, 5d21892c2e15b6a27f8bc907693eca7c6b7cc269, 705a412a367f383430fa34bada387af2e52eb043 |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Aug 16, 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/pf: Clear all LMTT pages on alloc Our LMEM buffer objects are not cleared by default on alloc and during VF provisioning we only setup LMTT PTEs for the actually provisioned LMEM range. But beyond that valid range we might leave some stale data that could either point to some other VFs allocations or even to the PF pages. Explicitly clear all new LMTT page to avoid the risk that a malicious VF would try to exploit that gap. While around add asserts to catch any undesired PTE overwrites and low-level debug traces to track LMTT PT life-cycle. (cherry picked from commit 3fae6918a3e27cce20ded2551f863fb05d4bef8d)
Quoted source text, attributed separately from HOL analysis.