drm/msm: make sure last_fence is always updated
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/msm: make sure last_fence is always updated
Update last_fence in the vm-bind path instead of kernel managed path.
last_fence is used to wait for work to finish in vm_bind contexts but not used for kernel managed contexts.
This fixes a bug where last_fence is not waited on context close leading to faults as resources are freed while in use.
Patchwork: https://patchwork.freedesktop.org/patch/680080/
From the CVE record · Linux
The Linux kernel drm/msm vm-bind path can fail to wait for in-flight work when a context closes, freeing resources while they are still in use and causing faults. The input does not establish whether an attacker can trigger this, or specify access, authentication, or user-interaction requirements.
Engineers running Linux kernels with drm/msm should check their versions; affected versions are not specified.