drm/msm: Fix VM_BIND UNMAP locking
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.18.337.0.107.1In the Linux kernel, the following vulnerability has been resolved:
drm/msm: Fix VM_BIND UNMAP locking
Wrong argument meant that the objs involved in UNMAP ops were not always getting locked.
Since _NO_SHARE objs share a common resv with the VM (which is always locked) this would only show up with non-_NO_SHARE BOs.
Patchwork: https://patchwork.freedesktop.org/patch/713898/
From the CVE record · Linux
The Linux kernel’s drm/msm VM_BIND UNMAP operations do not always lock the objects involved because of a wrong argument. The issue affects non-_NO_SHARE buffer objects; the input does not specify attacker capabilities, required access, or whether user interaction is needed.
Engineers running the Linux kernel should check whether their kernel includes the affected drm/msm code; affected versions are not specified.