Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.security > #6026
| From | piorunz <piorunz@gmx.com> |
|---|---|
| Newsgroups | linux.debian.security |
| Subject | Re: CVE-2017-5715 |
| Date | 2022-03-23 17:40 +0100 |
| Message-ID | <E4cbD-3GRX-13@gated-at.bofh.it> (permalink) |
| References | <E06xP-1dVd-3@gated-at.bofh.it> <E49GN-3Fic-5@gated-at.bofh.it> <E4atb-3FND-7@gated-at.bofh.it> <E4bpf-3GmO-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 23/03/2022 15:41, Leandro Cunha wrote: > Please, take into consideration what is in the link and you can consult through > it about CVE: https://security-tracker.debian.org/tracker/CVE-2017-5715 Leandro, I've been on this website before I posted with spectre-meltdown-checker results. I have vulnerable status just like author of this topic. I am on intel-microcode 3.20210608.2, and by the look of it, this bug supposed to be fixed in: "intel-microcode: Some microcode updates to partially adress CVE-2017-5715 included in 3.20171215.1 Further updates in 3.20180312.1" So my version of microcode is 3-4 years newer than that. Is it microcode problem, or spectre-meltdown-checker displaying wrong information, or something else entirely? -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄⠀⠀⠀⠀
Back to linux.debian.security | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
CVE-2017-5715 Georgi Naplatanov <gosho@oles.biz> - 2022-03-12 10:50 +0100
Re: CVE-2017-5715 piorunz <piorunz@gmx.com> - 2022-03-23 15:00 +0100
Re: CVE-2017-5715 Georgi Naplatanov <gosho@oles.biz> - 2022-03-23 15:50 +0100
Re: CVE-2017-5715 Leandro Cunha <leandrocunha016@gmail.com> - 2022-03-23 16:50 +0100
Re: CVE-2017-5715 Georgi Naplatanov <gosho@oles.biz> - 2022-03-23 17:20 +0100
Re: CVE-2017-5715 piorunz <piorunz@gmx.com> - 2022-03-23 17:40 +0100
Re: CVE-2017-5715 Georgi Naplatanov <gosho@oles.biz> - 2022-03-23 18:40 +0100
Re: CVE-2017-5715 Leandro Cunha <leandrocunha016@gmail.com> - 2022-03-23 21:50 +0100
Re: CVE-2017-5715 Georgi Naplatanov <gosho@oles.biz> - 2022-03-23 22:20 +0100
Re: CVE-2017-5715 Salvatore Bonaccorso <carnil@debian.org> - 2022-03-23 22:40 +0100
Re: CVE-2017-5715 Georgi Naplatanov <gosho@oles.biz> - 2022-03-24 09:00 +0100
Re: CVE-2017-5715 Leandro Cunha <leandrocunha016@gmail.com> - 2022-03-25 02:30 +0100
Re: CVE-2017-5715 Georgi Naplatanov <gosho@oles.biz> - 2022-03-25 08:20 +0100
Re: CVE-2017-5715 Leandro Cunha <leandrocunha016@gmail.com> - 2022-03-25 18:30 +0100
Re: CVE-2017-5715 Georgi Naplatanov <gosho@oles.biz> - 2022-03-25 18:40 +0100
Re: CVE-2017-5715 Leandro Cunha <leandrocunha016@gmail.com> - 2022-03-25 19:00 +0100
Re: CVE-2017-5715 Salvatore Bonaccorso <carnil@debian.org> - 2022-03-30 07:10 +0200
Re: CVE-2017-5715 Sylvestre Ledru <sylvestre@debian.org> - 2022-03-30 09:50 +0200
Re: CVE-2017-5715 Holger Levsen <holger@layer-acht.org> - 2022-03-30 11:40 +0200
Re: CVE-2017-5715 Salvatore Bonaccorso <carnil@debian.org> - 2022-04-06 06:40 +0200
csiph-web