From bf17094c87dea9586e72c2b18c612ba6c7d720c7 Mon Sep 17 00:00:00 2001
From: Mikaela Suomalainen This also affects Windows 10, but it doesn't expose this information or mitigation instructions as easily. When running a enough recent kernel, you can check the CPU vulnerabilities it detects by In case you have a Intel CPU, you will likely see that MDS - Microarchitectural Data Sampling is only partially mitigated ("SMT vulnerable"), unless you have disabled it in UEFI BIOS as the full mitigation disables Simultaneous multithreading which may be the cause of the highest performance impact. The following steps can be took to enable the full mitigation assuming your system/distribution uses grub and supports The following steps can be took to enable the full mitigation assuming your system/distribution uses grub and supports This also affects Windows 10, but it doesn't expose this information or mitigation instructions as easily. This also affects Windows 10, but it doesn't expose this information or mitigation instructions as easily. This also affects Windows 10, but it doesn't expose this information or mitigation instructions as easily. When running a enough recent kernel, you can check the CPU vulnerabilities it detects by In case you have a Intel CPU, you will likely see that MDS - Microarchitectural Data Sampling is only partially mitigated ("SMT vulnerable"), unless you have disabled it in UEFI BIOS as the full mitigation disables Simultaneous multithreading which may be the cause of the highest performance impact.
+ In case you have an Intel CPU, you may notice "SMT vulnerable" display after running the The following steps can be took to enable the full mitigation assuming your system/distribution uses grub and supports
tail -n +1 /sys/devices/system/cpu/vulnerabilities/*
. Vulnerable SMT can be disabled either in the UEFI BIOS or in kernel level by sudo mkdir /etc/default/grub.d/ && echo GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT mds=full,nosmt" | sudo tee /etc/default/grub.d/mds.conf && sudo update-grub
Worth Mentioning
--
2.47.2
From e7c1dde9d320f73a3a8fdfbce49ba6123eae876c Mon Sep 17 00:00:00 2001
From: Mikaela Suomalainen
+
+tail -n +1 /sys/devices/system/cpu/vulnerabilities/*
. Vulnerable SMT can be disabled either in the UEFI BIOS or in kernel level by sudo mkdir /etc/default/grub.d/ && echo GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT mds=full,nosmt" | sudo tee /etc/default/grub.d/mds.conf && sudo update-grub
Remember to check CPU vulnerability mitigations on Linux
+
+tail -n +1 /sys/devices/system/cpu/vulnerabilities/*
. By using tail -n +1
instead of cat
the file names are also visible./etc/default/grub.d/
:
+
+
+sudo mkdir /etc/default/grub.d/
to create a directory for additional grub configuration
+ echo GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT mds=full,nosmt" | sudo tee /etc/default/grub.d/mds.conf
to create a new grub config file source with the echoed contentsudo update-grub
to generate a new config file including these kernel flags
+ sudo reboot
to reboot
+ tail -n +1 /sys/devices/system/cpu/vulnerabilities/*
again to see that MDS now says SMT disabled.
+Further reading
+
+
+
Worth Mentioning
--
2.47.2
From ba9eefbd0ada7db4189949f27d4838b854fcd499 Mon Sep 17 00:00:00 2001
From: Mikaela Suomalainen
Remember to check CPU vulnerability mitigations on Linux
--
2.47.2
From a6f138a3830b39f78f5d3e2abbab0719760b0a2b Mon Sep 17 00:00:00 2001
From: Mikaela Suomalainen
--
2.47.2
From f9f7600ba5cae58d84f2124cca0828708e6f4738 Mon Sep 17 00:00:00 2001
From: Mikaela Suomalainen sudo mkdir /etc/default/grub.d/
to create a directory for additional grub configuration
echo GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT mds=full,nosmt" | sudo tee /etc/default/grub.d/mds.conf
to create a new grub config file source with the echoed contentsudo update-grub
to generate a new config file including these kernel flags
+ sudo grub-mkconfig -o /boot/grub/grub.cfg
(or on Debian/Ubuntu based distributions sudo update-grub
to generate a new config file including this new kernel flag
sudo reboot
to reboot
tail -n +1 /sys/devices/system/cpu/vulnerabilities/*
again to see that MDS now says SMT disabled.
/etc/default/grub.d/
:
-
sudo mkdir /etc/default/grub.d/
to create a directory for additional grub configuration
+ sudo mkdir /etc/default/grub.d/
to create a directory for additional grub configurationecho GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT mds=full,nosmt" | sudo tee /etc/default/grub.d/mds.conf
to create a new grub config file source with the echoed contentsudo grub-mkconfig -o /boot/grub/grub.cfg
(or on Debian/Ubuntu based distributions sudo update-grub
to generate a new config file including this new kernel flag
- sudo reboot
to reboot
- tail -n +1 /sys/devices/system/cpu/vulnerabilities/*
again to see that MDS now says SMT disabled.
+ sudo grub-mkconfig -o /boot/grub/grub.cfg
to generate a new config file including this new kernel flagsudo reboot
to reboottail -n +1 /sys/devices/system/cpu/vulnerabilities/*
again to see that MDS now says SMT disabled.Further reading
--
2.47.2
From 95ea0c871aba578e706631d22d8d94ee999e791a Mon Sep 17 00:00:00 2001
From: Mikaela Suomalainen
-Remember to check CPU vulnerability mitigations on Linux
+Remember to check CPU vulnerability mitigations
Remember to check CPU vulnerability mitigations
-tail -n +1 /sys/devices/system/cpu/vulnerabilities/*
. By using tail -n +1
instead of cat
the file names are also visible.tail
command. To mitigate this, disable hyper-threading from the UEFI/BIOS. You can also take the following mitigation steps below if your system/distribution uses GRUB and supports /etc/default/grub.d/
:
+/etc/default/grub.d/
:tail
command. To mitigate this, disable hyper-threading from the UEFI/BIOS. You can also take the following mitigation steps below if your system/distribution uses GRUB and supports /etc/default/grub.d/
:
The following steps can be took to enable the full mitigation assuming your system/distribution uses grub and supports /etc/default/grub.d/
:
sudo mkdir /etc/default/grub.d/
to create a directory for additional grub configurationecho GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT mds=full,nosmt" | sudo tee /etc/default/grub.d/mds.conf
to create a new grub config file source with the echoed contentsudo mkdir /etc/default/grub.d/
to create a directory for additional grub configurationecho GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT mds=full,nosmt" | sudo tee /etc/default/grub.d/mds.conf
to create a new grub config file source with the echoed contentsudo grub-mkconfig -o /boot/grub/grub.cfg
to generate a new config file including this new kernel flagsudo grub-mkconfig -o /boot/grub/grub.cfg
to generate a new grub config file including this new kernel flagsudo reboot
to reboottail -n +1 /sys/devices/system/cpu/vulnerabilities/*
again to see that MDS now says SMT disabled.echo GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT mds=full,nosmt" | sudo tee /etc/default/grub.d/mds.conf
to create a new grub config file source with the echoed contentsudo grub-mkconfig -o /boot/grub/grub.cfg
to generate a new grub config file including this new kernel flagsudo reboot
to reboottail -n +1 /sys/devices/system/cpu/vulnerabilities/*
again to see that MDS now says SMT disabled.tail -n +1 /sys/devices/system/cpu/vulnerabilities/*
again to see that MDS now says SMT disabled.This also affects Windows 10, but it doesn't expose this information or mitigation instructions as easily.
+This also affects Windows 10, but it doesn't expose this information or mitigation instructions as easily. MacOS users check How to enable full mitigation for Microarchitectural Data Sampling (MDS) vulnerabilities on Apple Support
When running a enough recent kernel, you can check the CPU vulnerabilities it detects by tail -n +1 /sys/devices/system/cpu/vulnerabilities/*
. By using tail -n +1
instead of cat
the file names are also visible.
This also affects Windows 10, but it doesn't expose this information or mitigation instructions as easily. MacOS users check How to enable full mitigation for Microarchitectural Data Sampling (MDS) vulnerabilities on Apple Support
-When running a enough recent kernel, you can check the CPU vulnerabilities it detects by tail -n +1 /sys/devices/system/cpu/vulnerabilities/*
. By using tail -n +1
instead of cat
the file names are also visible.
When running a enough recent kernel, you can check the CPU vulnerabilities it detects by tail -n +1 /sys/devices/system/cpu/vulnerabilities/*
. By using tail -n +1
instead of cat
, the file names are also visible.
In case you have an Intel CPU, you may notice "SMT vulnerable" display after running the tail
command. To mitigate this, disable hyper-threading from the UEFI/BIOS. You can also take the following mitigation steps below if your system/distribution uses GRUB and supports /etc/default/grub.d/
:
@@ -54,9 +54,9 @@ tor="http://sejnfjrq6szgca7v.onion"
sudo mkdir /etc/default/grub.d/
to create a directory for additional grub configurationecho GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT mds=full,nosmt" | sudo tee /etc/default/grub.d/mds.conf
to create a new grub config file source with the echoed contentsudo grub-mkconfig -o /boot/grub/grub.cfg
to generate a new grub config file including this new kernel flagsudo grub-mkconfig -o /boot/grub/grub.cfg
to generate a new grub config file including this new kernel boot flagsudo reboot
to reboottail -n +1 /sys/devices/system/cpu/vulnerabilities/*
again to see that MDS now says SMT disabled.tail -n +1 /sys/devices/system/cpu/vulnerabilities/*
again to see that MDS now says "SMT disabled."This also affects Windows 10, but it doesn't expose this information or mitigation instructions as easily. MacOS users check How to enable full mitigation for Microarchitectural Data Sampling (MDS) vulnerabilities on Apple Support
+This also affects Windows 10, but it doesn't expose this information or mitigation instructions as easily. MacOS users check How to enable full mitigation for Microarchitectural Data Sampling (MDS) vulnerabilities on Apple Support.
When running a enough recent kernel, you can check the CPU vulnerabilities it detects by tail -n +1 /sys/devices/system/cpu/vulnerabilities/*
. By using tail -n +1
instead of cat
, the file names are also visible.
When running a enough recent kernel, you can check the CPU vulnerabilities it detects by tail -n +1 /sys/devices/system/cpu/vulnerabilities/*
. By using tail -n +1
instead of cat
, the file names are also visible.
- In case you have an Intel CPU, you may notice "SMT vulnerable" display after running the tail
command. To mitigate this, disable hyper-threading from the UEFI/BIOS. You can also take the following mitigation steps below if your system/distribution uses GRUB and supports /etc/default/grub.d/
:
+ In case you have an Intel CPU, you may notice "SMT vulnerable" display after running the tail
command. To mitigate this, disable hyper-threading from the UEFI/BIOS. You can also take the following mitigation steps below if your system/distribution uses GRUB and supports /etc/default/grub.d/
: