drm/xe: Only use reserved BCS instances for usm migrate exec queue
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/xe: Only use reserved BCS instances for usm migrate exec queue
The GuC context scheduling queue is 2 entires deep, thus it is possible for a migration job to be stuck behind a fault if migration exec queue shares engines with user jobs. This can deadlock as the migrate exec queue is required to service page faults. Avoid deadlock by only using reserved BCS instances for usm migrate exec queue.
(cherry picked from commit 04f4a70a183a688a60fe3882d6e4236ea02cfc67)
From the CVE record · Linux
The Linux kernel’s drm/xe driver can deadlock when a migration execution queue shares engines with user jobs. A migration job can become stuck behind a fault, preventing the queue from servicing page faults. The input does not specify an attacker action, access requirements, or user interaction.
Engineers running Linux kernels with the drm/xe driver should check whether their kernel includes the fix; affected versions are not specified.