drm/xe: Use local fence in error path of xe_migrate_clear
- 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.25, 6.14.4
- 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: Use local fence in error path of xe_migrate_clear The intent of the error path in xe_migrate_clear is to wait on locally generated fence and then return. The code is waiting on m->fence which could be the local fence but this is only stable under the job mutex leading to a possible UAF. Fix code to wait on local fence. (cherry picked from commit 762b7e95362170b3e13a8704f38d5e47eca4ba74)
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From dd08ebf6c3525a7ea2186e636df064ea47281987 · fixed in 2ac5f466f62892a7d1ac2d1a3eb6cd14efbe2f2d; From dd08ebf6c3525a7ea2186e636df064ea47281987 · fixed in dc712938aa26b001f448d5e93f59d57fa80f2dbd; From dd08ebf6c3525a7ea2186e636df064ea47281987 · fixed in 20659d3150f1a2a258a173fe011013178ff2a197
- Linux Linux
6.8
- KernelLinux
From 6.8.0 · fixed in 6.12.25; From 6.13.0 · fixed in 6.14.4