From c0869d7341b2880bb5fdbd41176e784b0c826887 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?St=C3=A9phane=20Lesimple?= Date: Wed, 26 Jul 2023 16:30:20 +0200 Subject: [PATCH] enh: zenbleed: give a manual mitigation in --explain --- spectre-meltdown-checker.sh | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/spectre-meltdown-checker.sh b/spectre-meltdown-checker.sh index 6b64ea5..64972b5 100755 --- a/spectre-meltdown-checker.sh +++ b/spectre-meltdown-checker.sh @@ -6038,7 +6038,9 @@ check_CVE_2023_20593_linux() explain "Your CPU vendor may have a new microcode for your CPU model that mitigates this issue (refer to the hardware section above).\n " \ "Otherwise, the Linux kernel is able to mitigate this issue regardless of the microcode version you have, but in this case\n " \ "your kernel is too old to support this, your Linux distribution vendor might have a more recent version you should upgrade to.\n " \ -"Note that either having an up to date microcode OR an up to date kernel is enough to mitigate this issue." +"Note that either having an up to date microcode OR an up to date kernel is enough to mitigate this issue.\n " \ +"To manually mitigate the issue right now, you may use the following command: \`wrmsr -a 0xc0011029 \$((\$(rdmsr -c 0xc0011029) | (1<<9)))\`,\n " \ +"however note that this manual mitigation will only be active until the next reboot." fi unset zenbleed_print_vuln else