drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset()
authorDan Carpenter <dan.carpenter@oracle.com>
Wed, 4 Jul 2018 09:42:50 +0000 (12:42 +0300)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 29 Jan 2020 09:24:01 +0000 (10:24 +0100)
commit0c7f2cad142fcc87eebe60cc08bfb2ed1b44f719
treef940394dca94bebe3f0160ba41a998dc7d67c770
parent0decb42995078b9b48a0bfbe9f3884d88383ed2f
drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset()

[ Upstream commit 09c4b49457434fa74749ad6194ef28464d9f5df9 ]

This doesn't affect runtime because in the current code "idx" is always
valid.

First, we read from "vgdev->capsets[idx].max_size" before checking
whether "idx" is within bounds.  And secondly the bounds check is off by
one so we could end up reading one element beyond the end of the
vgdev->capsets[] array.

Fixes: 62fb7a5e1096 ("virtio-gpu: add 3d/virgl support")
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Link: http://patchwork.freedesktop.org/patch/msgid/20180704094250.m7sgvvzg3dhcvv3h@kili.mountain
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
drivers/gpu/drm/virtio/virtgpu_vq.c