drm/i915: mark requests for GuC virtual engines to avoid use-after-free
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.1.546.5.46.6In the Linux kernel, the following vulnerability has been resolved:
drm/i915: mark requests for GuC virtual engines to avoid use-after-free
References to i915_requests may be trapped by userspace inside a sync_file or dmabuf (dma-resv) and held indefinitely across different proceses. To counter-act the memory leaks, we try to not to keep references from the request past their completion. On the other side on fence release we need to know if rq->engine is valid and points to hw engine (true for non-virtual requests). To make it possible extra bit has been added to rq->execution_mask, for marking virtual engines.
(cherry picked from commit 280410677af763f3871b93e794a199cfcf6fb580)
From the CVE record · Linux
The Linux kernel’s drm/i915 driver has a use-after-free involving requests for GuC virtual engines. Local userspace can hold request references indefinitely through a sync_file or dmabuf, creating a risk when a fence is released; the input does not specify whether authentication or further user interaction is required.
Engineers running Linux systems that use the drm/i915 driver should check their kernel versions; affected versions are not specified.