drm/vmwgfx: reject DX_BIND_QUERY without a DX context
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9c079b8ce8bf8e0394149eb39c78b04285644bcc · < 55ec09c9ce10b1272802c7ab6c1be2ea0dbc68db| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/vmwgfx: reject DX_BIND_QUERY without a DX context
vmw_cmd_dx_bind_query() unconditionally dereferences sw_context->dx_ctx_node->ctx. Userspace can trigger a NULL pointer dereference from any render-node fd by submitting an execbuf with dx_context_handle == SVGA3D_INVALID_ID and a SVGA_3D_CMD_DX_BIND_QUERY opcode in the command stream: dx_ctx_node is left NULL and the kernel oopses on the assignment. The same NULL is then re-read in vmw_resources_reserve() via vmw_context_get_dx_query_mob().
All sibling DX handlers fail-close on a missing dx_ctx_node using VMW_GET_CTX_NODE(). Use the same pattern here, returning -EINVAL up front before any relocation state is published.
From the CVE record · Linux
The Linux kernel’s drm/vmwgfx DX_BIND_QUERY handler can dereference a NULL DX context. A local user with access to a render-node file descriptor can submit a crafted command stream that causes a kernel oops; no user interaction is described.
Engineers running Linux kernels with drm/vmwgfx should check whether their kernel includes the fix; affected versions are not specified.