drm/xe: Use local fence in error path of xe_migrate_clear
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.256.14.46.15In 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)
From the CVE record · Linux
The xe_migrate_clear error path in the Linux kernel’s drm/xe component can wait on a fence that is not stable without the job mutex, causing a possible use-after-free. The input does not specify how an attacker could trigger this path or whether authentication or user interaction is required.
Engineers running Linux kernels with the drm/xe component should check their installations; affected versions are not specified.