drm/vmwgfx: Make sure backup_handle is always valid
authorSinclair Yeh <syeh@vmware.com>
Fri, 2 Jun 2017 05:50:57 +0000 (07:50 +0200)
committerRaspbian kernel package updater <root@raspbian.org>
Sun, 23 Jul 2017 02:56:35 +0000 (02:56 +0000)
commit98e18d9ff0443ecf321dd8b2109ec3376d2bce35
treec6a8c67deb20bbe49fcba108db5e2ba0c2cffa39
parenta777cfb3d6db9dbbd30d9e9e3eff626a1946f817
drm/vmwgfx: Make sure backup_handle is always valid

commit 07678eca2cf9c9a18584e546c2b2a0d0c9a3150c upstream.

When vmw_gb_surface_define_ioctl() is called with an existing buffer,
we end up returning an uninitialized variable in the backup_handle.

The fix is to first initialize backup_handle to 0 just to be sure, and
second, when a user-provided buffer is found, we will use the
req->buffer_handle as the backup_handle.

Reported-by: Murray McAllister <murray.mcallister@insomniasec.com>
Signed-off-by: Sinclair Yeh <syeh@vmware.com>
Reviewed-by: Deepak Rawat <drawat@vmware.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/gpu/drm/vmwgfx/vmwgfx_surface.c