On 2020-06-29 19:22, Sreyan Chakravarty wrote: > > > On Mon, Jun 29, 2020 at 11:25 AM Samuel Sieb <samuel@xxxxxxxx <mailto:samuel@xxxxxxxx>> 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. > > Who else can I contact for this problem ? > > If a fix has been released why haven't I received it ? What's going on here ? > So, you're saying you get... [egreshko@meimei ~]$ rpm -q microcode_ctl microcode_ctl-2.1-39.fc32.x86_64 That is the version that is tagged is fixing the issue. And the problem still exists? If so, file a Bugzilla against that package. -- The key to getting good answers is to ask good questions. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
