drm/vmwgfx: Prevent unmapping active read buffers
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/vmwgfx: Prevent unmapping active read buffers
The kms paths keep a persistent map active to read and compare the cursor buffer. These maps can race with each other in simple scenario where: a) buffer "a" mapped for update b) buffer "a" mapped for compare c) do the compare d) unmap "a" for compare e) update the cursor f) unmap "a" for update At step "e" the buffer has been unmapped and the read contents is bogus.
Prevent unmapping of active read buffers by simply keeping a count of how many paths have currently active maps and unmap only when the count reaches 0.
From the CVE record · Linux
The Linux kernel’s drm/vmwgfx cursor paths can unmap a buffer while another path is still reading it, causing bogus read contents. The issue arises when cursor-buffer update and comparison mappings overlap; the input does not specify an attacker action, access requirements, or user interaction.
Engineers running Linux kernels that use drm/vmwgfx should check their versions against the vendor advisory; affected versions were not provided.