Skip to main content

linux - Spectre/Meltdown - update microcode

I am trying to manually update the microcode for the Intel i5-2410M.



Dell XPS 15z 2011 - Intel i5-2410M (Sandy bridge).



Ubuntu 18.04 (Debian) | Gnome | Grub2 | Systemd



I have installed some pre-packaged microcode from the Ubuntu repository, but I don't know if any of it applies to me:



apt install intel-microcode





dmsg | grep microcode



[ 0.000000] microcode: microcode updated early to revision 0x2d,
date = 2018-02-07




[ 1.259590] microcode: sig=0x206a7, pf=0x10, revision=0x2d



[ 1.259643] microcode: Microcode Update Driver: v2.2.




Note that the date is February 7, 2018.
Intel has a later release for the i5-2410M, April 25th 2018.





https://downloadcenter.intel.com/download/27776/Linux-Processor-Microcode-Data-File?product=52224






CVE-2018-3640 [rogue system register read] aka 'Variant 3a'




  • CPU microcode mitigates the vulnerability: NO





STATUS: VULNERABLE (an up-to-date CPU microcode is needed to mitigate this vulnerability)



How to fix: The microcode of your CPU needs to be upgraded to mitigate this vulnerability. This is usually done at boot time by your kernel (the upgrade is not persistent across reboots which is why it's done at each boot). If you're using a distro, make sure you are up to date, as microcode updates are usually shipped alongside with the distro kernel. Availability of a microcode update for you CPU model depends on your CPU vendor. You can usually find out online if a microcode update is available for your CPU by searching for your CPUID (indicated in the Hardware Check section). The microcode update is enough, there is no additional OS, kernel or software change needed.




CVE-2018-3639 [speculative store bypass] aka 'Variant 4'





  • Mitigated according to the /sys interface: NO (Vulnerable)


  • Kernel supports speculation store bypass: YES (found in /proc/self/status)





STATUS: VULNERABLE (Your CPU doesn't support SSBD)



How to fix: Your kernel is recent enough to use the CPU microcode features for mitigation, but your CPU microcode doesn't actually provide the necessary features for the kernel to use. The microcode of your CPU hence needs to be upgraded. This is usually done at boot time by your kernel (the upgrade is not persistent across reboots which is why it's done at each boot). If you're using a distro, make sure you are up to date, as microcode updates are usually shipped alongside with the distro kernel. Availability of a microcode update for you CPU model depends on your CPU vendor. You can usually find out online if a microcode update is available for your CPU by searching for your CPUID (indicated in the Hardware Check section).







» grep . /sys/devices/system/cpu/vulnerabilities/*



/sys/devices/system/cpu/vulnerabilities/meltdown:Mitigation: PTI



/sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Vulnerable




/sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: __user pointer sanitization



/sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full generic retpoline, IBPB, IBRS_FW




Could someone please provide a breadcrumb for what I should researching, I am stuck pretty good right now. I appreciate your time.

Comments

Post a Comment

Popular posts from this blog

linux - iDRAC6 Virtual Media native library cannot be loaded

When attempting to mount Virtual Media on a iDRAC6 IP KVM session I get the following error: I'm using Ubuntu 9.04 and: $ javaws -version Java(TM) Web Start 1.6.0_16 $ uname -a Linux aud22419-linux 2.6.28-15-generic #51-Ubuntu SMP Mon Aug 31 13:39:06 UTC 2009 x86_64 GNU/Linux $ firefox -version Mozilla Firefox 3.0.14, Copyright (c) 1998 - 2009 mozilla.org On Windows + IE it (unsurprisingly) works. I've just gotten off the phone with the Dell tech support and I was told it is known to work on Linux + Firefox, albeit Ubuntu is not supported (by Dell, that is). Has anyone out there managed to mount virtual media in the same scenario?
Post a Comment
Read more

ubuntu - Monitoring CPU, Mem, disk, on a single server

I've been looking for a simple starter solution for monitoring my [currently] single server hosted solution. Other than Nagios and similar, are there other good (simple) solutions people are using? Answer Everything depends on what you want. For example Munin is very simple, you can install and configure it in less then 10 minutes (on one server), it can sends alarms, make graphs from monitoring cpu, mem. apache connections, eaccellerator, disk io and many many more (it has many plugins). But if you are planning in future get some more machines, munin may not be enough. For example in munin you cant monitor state of individual processes, can't monitor changes in files (for security purpose). So if you wanna only see what is the utilization of basics parameters on your server and don't plan to buy some more servers Munin is what you are looking for, but if you wanna be alarmed when some of your service is down, take more control on what is happeninig on...
Post a Comment
Read more

hp proliant - Smart Array P822 with HBA Mode?

We get an HP DL360 G8 with an Smart Array P822 controller. On that controller will come a HP StorageWorks D2700 . Does anybody know, that it is possible to run the Smart Array P822 in HBA mode? I found only information about the P410i, who can run HBA. If this is not supported, what you think about the LSI 9207-8e controller? Will this fit good in that setup? The Hardware we get is used but all original from HP. The StorageWorks has 25 x 900 GB SAS 10K disks. Because the disks are not new I would like to use only 22 for raid6, and the rest for spare (I need to see if the disk count is optimal or not for zfs). It would be nice if I'm not stick to SAS in future. As OS I would like to install debian stretch with zfs 0.71 as file system and software raid. I have see that hp has an page for debian to. I would like to use hba mode because it is recommend, that zfs know at most as possible about the disk, and I'm independent from the raid controller. For us zfs have many benefits, ...
Post a Comment
Read more