Update to latest upstream release 20220510 / IPU 2022.1 to fix multiple security vulnerabilities
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
intel-microcode (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Impish |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
* Users are vulnerable to multiple security issues, including MMIO stale data (https:/
* Normally the security team would release updates direct to the -security pocket but since the associated kernels are being published via -updates *and* to allow phased updates to be used, it is preferred to publish these via -updates first, then they can be synced to -security once fully phased.
[Test Plan]
* install the updated intel-microcode packages and reboot the system
[Where problems could occur]
* Historically there have been issues where intel-microcode updates resulted in machines that fail to boot. This has usually been the case when a machine is using an old BIOS and the microcode which is loaded in early boot is much newer. Intel have increased their own internal testing to try and ensure this is detected before releasing to production.
Also these updates have now been in -proposed for over a week without any mention of issues *plus* they have been tested extensively via testflinger on the Canonical certification lab's suite of machines too.
Finally, in this unlikely case, users can boot via the '(recovery mode)' menu entries in grub which disables early microcode loading from the initrd to workaround this and then rollback the microcode update directly.
[Other Info]
Intel released version 20220510 / IPU 2022.1 earlier in May to address multiple vulnerabilities, including:
- CVE-2022-21151, INTEL-SA-00617
- CVE-2021-0146, INTEL-SA-00528
- CVE-2021-0127, INTEL-SA-00532
This version is already packaged in Ubuntu 22.10 (kinetic).
Earlier today Intel disclosed another set of vulnerabilities (MMIO stale data) which are also fixed by these updates.
Whilst this is a security update, to allow for increased testing before being more widely deployed the Ubuntu Security team are wishing to publish this first via -proposed and then to -updates so they can be phased along with the associated kernel updates for MMIO stale data as well.
CVE References
tags: | added: block-proposed-bionic |
tags: | added: block-proposed-focal block-proposed-impish block-proposed-jammy |
Changed in intel-microcode (Ubuntu Bionic): | |
status: | New → Fix Committed |
Changed in intel-microcode (Ubuntu Focal): | |
status: | New → Fix Committed |
Changed in intel-microcode (Ubuntu Impish): | |
status: | New → Fix Committed |
Changed in intel-microcode (Ubuntu Jammy): | |
status: | New → Fix Committed |
description: | updated |
tags: |
added: verification-done verification-done-bionic verification-done-focal verification-done-impish verification-done-jammy removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-impish verification-needed-jammy |
Hello Alex, or anyone else affected,
Accepted intel-microcode into jammy-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ intel-microcode /3.20220510. 0ubuntu0. 22.04.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification- needed- jammy to verification- done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed- jammy. In either case, without details of your testing we will not be able to proceed.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance for helping!
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.