--- title: 'USN-4182-1: Intel Microcode update | Ubuntu security notices' description: Ubuntu is an open source software operating system that runs from the desktop, to the cloud, to all your internet connected things. url: https://ubuntu.com/security/notices/USN-4182-1 --- 1. [Ubuntu Security Notices](https://ubuntu.com/security/notices) 2. USN-4182-1 --- # USN-4182-1: Intel Microcode update Publication date 12 November 2019 Overview Several security issues were fixed in Intel Microcode. Releases [19.10](https://ubuntu.com/security/notices?release=eoan) [19.04](https://ubuntu.com/security/notices?release=disco) [18.04 LTS](https://ubuntu.com/security/notices?release=bionic) [16.04 LTS](https://ubuntu.com/security/notices?release=xenial) --- Open side navigation ## Packages * [intel-microcode](https://ubuntu.com/security/cves?package=intel-microcode) - Processor microcode for Intel CPUs ## Details Stephan van Schaik, Alyssa Milburn, Sebastian Österlund, Pietro Frigo, Kaveh Razavi, Herbert Bos, Cristiano Giuffrida, Giorgi Maisuradze, Moritz Lipp, Michael Schwarz, Daniel Gruss, and Jo Van Bulck discovered that Intel processors using Transactional Synchronization Extensions (TSX) could expose memory contents previously stored in microarchitectural buffers to a malicious process that is executing on the same CPU core. A local attacker could use this to expose sensitive information. ([CVE-2019-11135](https://ubuntu.com/security/CVE-2019-11135)) It was discovered that certain Intel Xeon processors did not properly restrict access to a voltage modulation interface. A local privileged attacker could use this to cause a denial of service (system crash). ([CVE-2019-11139](https://ubuntu.com/security/CVE-2019-11139)) ## Update instructions After a standard system update you need to reboot your computer. Please note that in order to fully mitigate CVE-2019-11139, a warm reboot is required \*after\* applying the microcode update; so in effect a second reboot. [Learn more about how to get the fixes.](https://ubuntu.com/security/cves/about#security) The problem can be corrected by updating your system to the following package versions: | Ubuntu Release | Package Version | | --- | --- | | 19.10 eoan | [intel-microcode](https://launchpad.net/ubuntu/+source/intel-microcode) –  [3.20191112-0ubuntu0.19.10.2](https://launchpad.net/ubuntu/+source/intel-microcode/3.20191112-0ubuntu0.19.10.2) | | | | 19.04 disco | [intel-microcode](https://launchpad.net/ubuntu/+source/intel-microcode) –  [3.20191112-0ubuntu0.19.04.2](https://launchpad.net/ubuntu/+source/intel-microcode/3.20191112-0ubuntu0.19.04.2) | | | | 18.04 LTS bionic | [intel-microcode](https://launchpad.net/ubuntu/+source/intel-microcode) –  [3.20191112-0ubuntu0.18.04.2](https://launchpad.net/ubuntu/+source/intel-microcode/3.20191112-0ubuntu0.18.04.2) | | | | 16.04 LTS xenial | [intel-microcode](https://launchpad.net/ubuntu/+source/intel-microcode) –  [3.20191112-0ubuntu0.16.04.2](https://launchpad.net/ubuntu/+source/intel-microcode/3.20191112-0ubuntu0.16.04.2) | | | --- ### Reduce your security exposure Ubuntu Pro provides ten-year security coverage to 25,000+ packages in Main and Universe repositories, and it is free for up to five machines. [Get Ubuntu Pro](https://ubuntu.com/pro) ## References * * [CVE-2019-11139](https://ubuntu.com/security/CVE-2019-11139) * [CVE-2019-11135](https://ubuntu.com/security/CVE-2019-11135) ## Related notices * [USN-4188-1](https://ubuntu.com/security/notices/USN-4188-1) * [USN-4187-1](https://ubuntu.com/security/notices/USN-4187-1) * [USN-4186-1](https://ubuntu.com/security/notices/USN-4186-1) * [USN-4186-2](https://ubuntu.com/security/notices/USN-4186-2) * [USN-4185-2](https://ubuntu.com/security/notices/USN-4185-2) * [USN-4185-1](https://ubuntu.com/security/notices/USN-4185-1) * [USN-4184-1](https://ubuntu.com/security/notices/USN-4184-1) * [USN-4183-1](https://ubuntu.com/security/notices/USN-4183-1) * [USN-4182-2](https://ubuntu.com/security/notices/USN-4182-2)