Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.security > #5909
| From | Christoph Pflügler <christoph@pfluegler.net> |
|---|---|
| Newsgroups | linux.debian.security |
| Subject | Re: intel-microcode not fixing CVE-2018-3640, CVE-2018-3615 on Debian 10? |
| Date | 2021-01-13 22:00 +0100 |
| Message-ID | <BwVpg-8gd-5@gated-at.bofh.it> (permalink) |
| References | (3 earlier) <Bv8JX-83S-1@gated-at.bofh.it> <BvnIZ-qp-7@gated-at.bofh.it> <Bvsz0-3ny-15@gated-at.bofh.it> <BwuS7-NP-27@gated-at.bofh.it> <BwR2h-5So-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 13.01.21 17:15, Michael Stone wrote: > On Tue, Jan 12, 2021 at 05:25:23PM +0100, Giacomo Catenazzi wrote: >> In any case, according Intel, microcode should be updated by BIOS > > I wonder if anyone from intel can manage to say that with a straight > face. > This is the dmesg | grep microcode output for the i5 gen3: [ 0.000000] microcode: microcode updated early to revision 0x21, date = 2019-02-13 [ 0.222193] SRBDS: Vulnerable: No microcode [ 1.067686] microcode: sig=0x306a9, pf=0x10, revision=0x21 [ 1.067856] microcode: Microcode Update Driver: v2.2. and here the one for the E3 v5: [ 0.000000] microcode: microcode updated early to revision 0xd6, date = 2019-10-03 [ 0.379026] SRBDS: Vulnerable: No microcode [ 1.625090] microcode: sig=0x506e3, pf=0x2, revision=0xd6 [ 1.625215] microcode: Microcode Update Driver: v2.2. Seems like the microcode is applied to my CPUs. This is also supported by numerous other CVEs getting mitigated after intel-microcode installation. I also tried the latest meltdown-spectre-checker (v0.44), the results are the same (plus another red 2020 CVE).
Back to linux.debian.security | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
intel-microcode not fixing CVE-2018-3640, CVE-2018-3615 on Debian 10? Christoph Pflügler <christoph@pfluegler.net> - 2021-01-08 21:30 +0100
Re: intel-microcode not fixing CVE-2018-3640, CVE-2018-3615 on Debian 10? Christoph Pflügler <christoph@pfluegler.net> - 2021-01-08 22:50 +0100
Re: intel-microcode not fixing CVE-2018-3640, CVE-2018-3615 on Debian 10? Michael Stone <mstone@debian.org> - 2021-01-08 23:50 +0100
Re: intel-microcode not fixing CVE-2018-3640, CVE-2018-3615 on Debian 10? Christoph Pflügler <christoph@pfluegler.net> - 2021-01-09 15:50 +0100
Re: intel-microcode not fixing CVE-2018-3640, CVE-2018-3615 on Debian 10? James Wallen <jpwallen@comcast.net> - 2021-01-09 21:00 +0100
Re: intel-microcode not fixing CVE-2018-3640, CVE-2018-3615 on Debian 10? Giacomo Catenazzi <cate@debian.org> - 2021-01-12 17:40 +0100
Re: intel-microcode not fixing CVE-2018-3640, CVE-2018-3615 on Debian 10? Michael Stone <mstone@debian.org> - 2021-01-13 17:20 +0100
Re: intel-microcode not fixing CVE-2018-3640, CVE-2018-3615 on Debian 10? Christoph Pflügler <christoph@pfluegler.net> - 2021-01-13 22:00 +0100
Re: intel-microcode not fixing CVE-2018-3640, CVE-2018-3615 on Debian 10? Michael Stone <mstone@debian.org> - 2021-01-14 00:00 +0100
Re: intel-microcode not fixing CVE-2018-3640, CVE-2018-3615 on Debian 10? Christoph Pflügler <christoph@pfluegler.net> - 2021-01-14 18:30 +0100
Re: intel-microcode not fixing CVE-2018-3640, CVE-2018-3615 on Debian 10? Michael Stone <mstone@debian.org> - 2021-01-08 22:50 +0100
csiph-web