drm/xe/pf: Clear all LMTT pages on alloc
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.12.396.15.76.16In 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)
From the CVE record · Linux
During VF provisioning, newly allocated LMTT pages may contain stale entries beyond the provisioned LMEM range. A malicious VF could potentially use those entries to access another VF’s allocations or PF pages. Exploitation requires access to a VF; the input does not specify whether additional authentication or user interaction is needed.
Engineers running the Linux kernel with drm/xe VF provisioning should check their systems; affected versions are not specified.