drm/virtio: Ensure that objs is not NULL in virtio_gpu_array_put_free()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| 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/virtio: Ensure that objs is not NULL in virtio_gpu_array_put_free()
If virtio_gpu_object_shmem_init() fails (e.g. due to fault injection, as it happened in the bug report by syzbot), virtio_gpu_array_put_free() could be called with objs equal to NULL.
Ensure that objs is not NULL in virtio_gpu_array_put_free(), or otherwise return from the function.
From the CVE record · Linux
The Linux kernel’s virtio GPU code could call virtio_gpu_array_put_free() with a NULL object array if virtio_gpu_object_shmem_init() fails. This could cause a NULL pointer dereference; the input does not establish an attacker access path or authentication or user-interaction requirements.
Teams running Linux kernels with the virtio GPU code should check their kernel versions; affected versions are not specified.