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)
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://git.kernel.org/stable/c/5d21892c2e15b6a27f8bc907693eca7c6b7cc269 Patch
- https://git.kernel.org/stable/c/705a412a367f383430fa34bada387af2e52eb043 Patch
- https://git.kernel.org/stable/c/ff4b8c9ade1b82979fdd01e6f45b60f92eed26d8 Patch
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.5 · linuxNVD modified 2026-10-15 22:18
Affected (CPE criteria) 6
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.16:rc1:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.16:rc2:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.16:rc3:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.16:rc4:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.16:rc5:*:*:*:*:*:*