diff options
author | Ben Hutchings <ben@decadent.org.uk> | 2024-03-11 00:14:13 +0100 |
---|---|---|
committer | Ben Hutchings <ben@decadent.org.uk> | 2024-03-11 00:14:13 +0100 |
commit | 2c4b85f17d5be4ef479402b9fbf18f22522dced7 (patch) | |
tree | d4075c0b35bd521e75c2a4ac7ce524466daff95d /active/CVE-2023-3640 | |
parent | 73dccfc63d792093db024dd1df1e7dfd4682bac2 (diff) |
Mark CVE-2023-3640 as ignored in all suites
This issue seems to be a known and unfixable limitation to Meltdown
mitigation on x86.
Diffstat (limited to 'active/CVE-2023-3640')
-rw-r--r-- | active/CVE-2023-3640 | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/active/CVE-2023-3640 b/active/CVE-2023-3640 index a4e128ecb..c53a1b515 100644 --- a/active/CVE-2023-3640 +++ b/active/CVE-2023-3640 @@ -6,11 +6,11 @@ Notes: 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: -5.10-upstream-stable: -4.19-upstream-stable: -sid: -6.1-bookworm-security: -5.10-bullseye-security: -4.19-buster-security: +upstream: ignored "Unfixable CPU issue" +6.1-upstream-stable: ignored "Unfixable CPU issue" +5.10-upstream-stable: ignored "Unfixable CPU issue" +4.19-upstream-stable: ignored "Unfixable CPU issue" +sid: ignored "Unfixable CPU issue" +6.1-bookworm-security: ignored "Unfixable CPU issue" +5.10-bullseye-security: ignored "Unfixable CPU issue" +4.19-buster-security: ignored "Unfixable CPU issue" |