Christian Borntraeger 0447819741 KVM: s390: do not expose random data via facility bitmap ... kvm_s390_get_machine() populates the facility bitmap by copying bytes from the host results that are stored in a 256 byte array in the prefix page. The KVM code does use the size of the target buffer (2k), thus copying and exposing unrelated kernel memory (mostly machine check related logout data). Let's use the size of the source buffer instead. This is ok, as the target buffer will always be greater or equal than the source buffer as the KVM internal buffers (and thus S390_ARCH_FAC_LIST_SIZE_BYTE) cover the maximum possible size that is allowed by STFLE, which is 256 doublewords. All structures are zero allocated so we can leave bytes 256-2047 unchanged. Add a similar fix for kvm_arch_init_vm(). Reported-by: Heiko Carstens <heiko.carstens@de.ibm.com> [found with smatch] Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com> CC: stable@vger.kernel.org Acked-by: Cornelia Huck <cornelia.huck@de.ibm.com>		2017-01-20 15:29:34 +01:00
..
diag.c
gaccess.c
gaccess.h
guestdbg.c
intercept.c
interrupt.c	ktime: Cleanup ktime_set() usage	2016-12-25 17:21:22 +01:00
irq.h
Kconfig
kvm-s390.c	KVM: s390: do not expose random data via facility bitmap	2017-01-20 15:29:34 +01:00
kvm-s390.h
Makefile
priv.c
sigp.c
sthyi.c	KVM: s390: Fix STHYI buffer alignment for diag224	2016-10-26 13:46:44 +02:00
trace-s390.h
trace.h
vsie.c