This bug was fixed in the package intel-microcode -
3.20190618.0ubuntu0.18.10.1
---
intel-microcode (3.20190618.0ubuntu0.18.10.1) cosmic-security; urgency=medium
* SECURITY UPDATE: New upstream microcode datafile 20190618
- CVE-2018-12126, CVE-2018-12127, CVE-2018-12130,
This bug was fixed in the package intel-microcode -
3.20190618.0ubuntu0.16.04.1
---
intel-microcode (3.20190618.0ubuntu0.16.04.1) xenial-security; urgency=medium
* SECURITY UPDATE: New upstream microcode datafile 20190618
- CVE-2018-12126, CVE-2018-12127, CVE-2018-12130,
Hello,
Release 20190618 is out, and has these updates.
I uploaded it to Debian unstable a few hours agoand we will issue it as
a security update as well soon.
I imagine Ubuntu will do the same.
--
Henrique de Moraes Holschuh
--
You received this bug notification because you are a member
On 2019-06-19 04:40:20, Wenhan Shi wrote:
> Do we have a timeline about when Intel will fix this bug?
No, the bug fixing process isn't that predictable. They are actively
working on it and they're occasionally providing status updates in the
upstream bug report:
Hi
Do we have a timeline about when Intel will fix this bug?
Wenhan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830123
Title:
intel-microcode 20190514 does not provide Sandy Bridge (sigs
