Re: [Qemu-devel] [PATCH] virtio-gpu: fix information leak in capset get dispatch

[Marc-André Lureau]

Hi

On Tue, Nov 1, 2016 at 3:38 PM Li Qiang <address@hidden> wrote:

> From: Li Qiang <address@hidden>
>
> In virgl_cmd_get_capset function, it uses g_malloc to allocate
> a response struct to the guest. As the 'resp'struct hasn't been full
> initialized it will lead the 'resp->padding' field to the guest.
> Use g_malloc0 to avoid this.
>
> Signed-off-by: Li Qiang <address@hidden>
>

I was about to point out this in the previous memset patch

Reviewed-by: Marc-André Lureau <address@hidden>


---
>  hw/display/virtio-gpu-3d.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/display/virtio-gpu-3d.c b/hw/display/virtio-gpu-3d.c
> index 23f39de..d98b140 100644
> --- a/hw/display/virtio-gpu-3d.c
> +++ b/hw/display/virtio-gpu-3d.c
> @@ -371,7 +371,7 @@ static void virgl_cmd_get_capset(VirtIOGPU *g,
>
>      virgl_renderer_get_cap_set(gc.capset_id, &max_ver,
>                                 &max_size);
> -    resp = g_malloc(sizeof(*resp) + max_size);
> +    resp = g_malloc0(sizeof(*resp) + max_size);
>
>      resp->hdr.type = VIRTIO_GPU_RESP_OK_CAPSET;
>      virgl_renderer_fill_caps(gc.capset_id,
> --
> 1.8.3.1
>
>
> --
Marc-André Lureau