Description: KVM: X86: Fix stack-out-of-bounds read in write_mmio References: https://www.spinics.net/lists/kvm/msg160710.html https://www.spinics.net/lists/kvm/msg160796.html Notes: bwh> This appears to only affect the write_mmio tracepoint, so it won't do any bwh> harm unless that tracepoint is enabled. Introduced in 2.6.32 by commit bwh> aec51dc4f158 "KVM: Trace mmio". Bugs: upstream: released (4.15-rc5) [e39d200fa5bf5b94a0948db0dae44c1b73b84a56] 4.9-upstream-stable: released (4.9.77) [c781e3be97a1cbeef8c853101e8f266db556b0a3] 3.16-upstream-stable: released (3.16.52) [7cc7f67418296f829a284b6e2d4c62d937f15faa] 3.2-upstream-stable: released (3.2.97) [26a8a3c531ae847048ee9126f07cb07424bd4724] sid: released (4.14.7-1) [bugfix/all/kvm-fix-stack-out-of-bounds-read-in-write_mmio.patch] 4.9-stretch-security: released (4.9.65-3+deb9u1) [bugfix/all/kvm-fix-stack-out-of-bounds-read-in-write_mmio.patch] 3.16-jessie-security: released (3.16.51-3+deb8u1) [bugfix/all/kvm-fix-stack-out-of-bounds-read-in-write_mmio.patch] 3.2-wheezy-security: released (3.2.96-3) [bugfix/x86/kvm-fix-stack-out-of-bounds-read-in-write_mmio.patch]