summaryrefslogtreecommitdiffstats
path: root/active/CVE-2020-36310
diff options
context:
space:
mode:
authorBen Hutchings <ben@decadent.org.uk>2022-03-02 15:55:00 +0100
committerBen Hutchings <ben@decadent.org.uk>2022-03-02 15:55:56 +0100
commit3ea3e034d22efb58bf2c2522c8eb9814b1447263 (patch)
tree44b68be660d813532abc8d554023808a400d619b /active/CVE-2020-36310
parente43978202961d8fce9012a103391a97965434cea (diff)
Record the actual fix for CVE-2020-36310
Diffstat (limited to 'active/CVE-2020-36310')
-rw-r--r--active/CVE-2020-363108
1 files changed, 5 insertions, 3 deletions
diff --git a/active/CVE-2020-36310 b/active/CVE-2020-36310
index f61db03ca..89b28f61d 100644
--- a/active/CVE-2020-36310
+++ b/active/CVE-2020-36310
@@ -4,12 +4,14 @@ References:
Notes:
bwh> Appears to have been introduced in 4.17 by commit 00b10fe1046c
bwh> "KVM: X86: Restart the guest when insn_len is zero and SEV is enabled".
+ bwh> Initially supposed to be fixed by e72436bc3a52 "KVM: SVM: avoid
+ bwh> infinite loop on NPF from bad address", but that was flawed.
Bugs:
-upstream: released (5.8-rc1) [e72436bc3a5206f95bb384e741154166ddb3202e]
-5.10-upstream-stable: N/A "Fixed before branching point"
+upstream: released (5.17-rc2) [55467fcd55b89c622e62b4afe60ac0eb2fae91f2]
+5.10-upstream-stable: released (5.10.102) [9dcedbe943be8c93722c1ed68b59001b28b0d889]
4.19-upstream-stable: needed
4.9-upstream-stable: N/A "Vulnerability introduced later"
sid: released (5.8.7-1)
-5.10-bullseye-security: N/A "Fixed before branching point"
+5.10-bullseye-security: needed
4.19-buster-security: needed
4.9-stretch-security: N/A "Vulnerability introduced later"

© 2014-2024 Faster IT GmbH | imprint | privacy policy