On 2020-06-29 13:54, Samuel Sieb wrote: > On 6/28/20 10:03 PM, Ed Greshko wrote: >> On 2020-06-29 07:33, Sreyan Chakravarty wrote: >>> * SRBDS mitigation control is enabled and active: NO >>>> STATUS: VULNERABLE (Your CPU microcode may need to be updated to >>>> mitigate the vulnerability) >> >> CVE-2020-0543 aka 'Special Register Buffer Data Sampling (SRBDS)' >> * Mitigated according to the /sys interface: YES (Not affected) >> * SRBDS mitigation control is supported by the kernel: YES (found SRBDS >> implementation evidence in kernel image. Your kernel is up to date for SRBDS >> mitigation) >> * SRBDS mitigation control is enabled and active: NO >>> STATUS: NOT VULNERABLE (your CPU vendor reported your CPU model as not >>> vulnerable) > > Notice the reason that yours is not vulnerable. You have a different CPU > model that doesn't have the problem.
Good point. Didn't read far enough. :-( Yet.... https://lists.fedoraproject.org/archives/list/package-annou...@lists.fedoraproject.org/message/T5OUM24ZC43G4IDT3JUCIHJTSDXJSK6Y/ Indicates.... Update Information: Security fix for CVE-2020-0548, CVE-2020-0549, CVE-2020-0543 ---- Update to upstream 2.1-28. 20200609 So, shouldn't that take care of CPU's that are vulnerable? -- The key to getting good answers is to ask good questions. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
