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

> A malicious virtual function could read stale memory from the physical function or other virtual functions due to uncleared LMTT pages in the Linux kernel.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Aug 2025
- **Updated:** 15 Oct 2026
- **Also known as:** BELL-CVE-2025-38511, DEBIAN-CVE-2025-38511, GHSA-59vp-pw3x-2g3w, ROOT-OS-DEBIAN-13-CVE-2025-38511, ROOT-OS-UBUNTU-2404-CVE-2025-38511, UBUNTU-CVE-2025-38511

## What is CVE-2025-38511?

CVE-2025-38511 is a high-severity vulnerability in Linux kernel, published on 16 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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)

## Which versions are affected by CVE-2025-38511?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2025-38511?

Apply the vendor's patch.

## Is CVE-2025-38511 being exploited?

There is no known exploitation of CVE-2025-38511 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-38511 and fix it if it is affected.

What it is: CVE-2025-38511 is a high-severity vulnerability in Linux kernel, published on 16 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-38511 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-38511/ (Markdown: https://insights.sbomify.com/CVE-2025-38511/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-38511
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-38511
- OSV: https://osv.dev/vulnerability/CVE-2025-38511

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-38511/
Summaries are generated and may contain mistakes; the official description above is the record.