summaryrefslogtreecommitdiffstats
path: root/active/CVE-2023-3640
diff options
context:
space:
mode:
authorBen Hutchings <ben@decadent.org.uk>2023-12-19 00:16:13 +0100
committerBen Hutchings <ben@decadent.org.uk>2023-12-19 00:16:13 +0100
commit19b105c9ec13e71db8ed9f0bc52f16712c2ec08a (patch)
tree2db18645146c3afd79778f866c20d20d66de02e2 /active/CVE-2023-3640
parent65297c7e39d2fcb33e1025e80c52c8d8c0f6d9ce (diff)
Fill in status for several issues
Diffstat (limited to 'active/CVE-2023-3640')
-rw-r--r--active/CVE-2023-36403
1 files changed, 3 insertions, 0 deletions
diff --git a/active/CVE-2023-3640 b/active/CVE-2023-3640
index ae6482fc4..a4e128ecb 100644
--- a/active/CVE-2023-3640
+++ b/active/CVE-2023-3640
@@ -2,6 +2,9 @@ Description: x86/mm: a per-cpu entry area leak was identified through the init_c
References:
https://bugzilla.redhat.com/show_bug.cgi?id=2217523
Notes:
+ bwh> From the description on RHBZ, this seems like the unfixable residual
+ bwh> effect of Meltdown and not a new issue. There's no claim that kernel
+ bwh> memory outside of the entry area can be read.
Bugs:
upstream:
6.1-upstream-stable:

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