drm/xe/pf: Clear all LMTT pages on alloc
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.12.39, 6.15.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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)
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From b1d20405821812ad70d95eefe58cadc6d50b0917 · fixed in ff4b8c9ade1b82979fdd01e6f45b60f92eed26d8; From b1d20405821812ad70d95eefe58cadc6d50b0917 · fixed in 5d21892c2e15b6a27f8bc907693eca7c6b7cc269; From b1d20405821812ad70d95eefe58cadc6d50b0917 · fixed in 705a412a367f383430fa34bada387af2e52eb043
- Linux Linux
6.8
- KernelLinux
From 6.8.0 · fixed in 6.12.39; From 6.13.0 · fixed in 6.15.7