From 6a6e97210d5f828344fa6de140fa28c7375c448d Mon Sep 17 00:00:00 2001 From: Ben Hutchings Date: Sat, 10 Aug 2019 21:44:09 +0100 Subject: Unmark CVE-2019-kvm-guest-xcr0 as pending for 3.16-upstream-stable The fix requires backporting several more changes and I'm not confident about them so I've dropped it for now. --- active/CVE-2019-kvm-guest-xcr0 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'active/CVE-2019-kvm-guest-xcr0') diff --git a/active/CVE-2019-kvm-guest-xcr0 b/active/CVE-2019-kvm-guest-xcr0 index e55b2e46..8042ef15 100644 --- a/active/CVE-2019-kvm-guest-xcr0 +++ b/active/CVE-2019-kvm-guest-xcr0 @@ -3,12 +3,12 @@ References: Notes: bwh> Branches before 4.14 should probably apply commit b060ca3b2e9e bwh> "kvm: vmx: Handle VMLAUNCH/VMRESUME failure properly" first, if - bwh> only to avoid conflicts. + bwh> only to avoid conflicts. But this in turn needs further fixes. Bugs: upstream: released (5.1-rc6) [1811d979c71621aafc7b879477202d286f7e863b] 4.19-upstream-stable: needed 4.9-upstream-stable: needed -3.16-upstream-stable: pending (3.16.72) [x86-kvm-move-kvm_load-put_guest_xcr0-into-atomic-context.patch] +3.16-upstream-stable: needed sid: released (5.2.6-1) 4.19-buster-security: needed 4.9-stretch-security: needed -- cgit v1.2.3