Page 22 of 22 FirstFirst ... 12202122
Results 211 to 211 of 211

Thread: Meltdown and Spectre Discussion Sticky

  1. #211
    Join Date
    Oct 2008
    Location
    Rezzoaglio (GE) Italy
    Beans
    257
    Distro
    Ubuntu Development Release

    Re: Meltdown and Spectre Discussion Sticky

    On my PC meltdown-checker find 2 vulnerabilities on Ubuntu 19.10 with kernel 5.3.0-22-generic
    but NO vulnerabilities on Ubuntu 19.04 w kernel 5.0.0-32-generic

    Code:
    corrado@corrado-p6-eoan-1017:~$ sudo ./spectre-meltdown-checker.sh
    [sudo] password for corrado: 
    Spectre and Meltdown mitigation detection tool v0.42
    
    Checking for vulnerabilities on current system
    Kernel is Linux 5.3.0-22-generic #24-Ubuntu SMP Sat Nov 9 17:34:30 UTC 2019 x86_64
    CPU is Intel(R) Core(TM) i3-7100 CPU @ 3.90GHz
    
    Hardware check
    * Hardware support (CPU microcode) for mitigation techniques
      * Indirect Branch Restricted Speculation (IBRS)
        * SPEC_CTRL MSR is available: intel_rapl_msr 20480 0 - Live 0xffffffffc0873000
    intel_rapl_common 24576 1 intel_rapl_msr, Live 0xffffffffc0839000
     UNKNOWN  (is msr kernel module available?)
        * CPU indicates IBRS capability:  YES  (SPEC_CTRL feature bit)
      * Indirect Branch Prediction Barrier (IBPB)
        * PRED_CMD MSR is available:  UNKNOWN  (is msr kernel module available?)
        * CPU indicates IBPB capability:  YES  (SPEC_CTRL feature bit)
      * Single Thread Indirect Branch Predictors (STIBP)
        * SPEC_CTRL MSR is available:  UNKNOWN  (is msr kernel module available?)
        * CPU indicates STIBP capability:  YES  (Intel STIBP feature bit)
      * Speculative Store Bypass Disable (SSBD)
        * CPU indicates SSBD capability:  YES  (Intel SSBD)
      * L1 data cache invalidation
        * FLUSH_CMD MSR is available:  UNKNOWN  (is msr kernel module available?)
        * CPU indicates L1D flush capability:  YES  (L1D flush feature bit)
      * Microarchitectural Data Sampling
        * VERW instruction is available:  YES  (MD_CLEAR feature bit)
      * TSX Asynchronous Abort
        * TSX support is available:  NO 
      * Enhanced IBRS (IBRS_ALL)
        * CPU indicates ARCH_CAPABILITIES MSR availability:  NO 
        * ARCH_CAPABILITIES MSR advertises IBRS_ALL capability:  NO 
      * CPU explicitly indicates not being vulnerable to Meltdown/L1TF (RDCL_NO):  NO 
      * CPU explicitly indicates not being vulnerable to Variant 4 (SSB_NO):  NO 
      * CPU/Hypervisor indicates L1D flushing is not necessary on this system:  NO 
      * Hypervisor indicates host CPU might be vulnerable to RSB underflow (RSBA):  NO 
      * CPU explicitly indicates not being vulnerable to Microarchitectural Data Sampling (MDS_NO):  NO 
      * CPU explicitly indicates not being vulnerable to TSX Asynchrnonous Abort (TAA_NO):  NO 
      * CPU supports Software Guard Extensions (SGX):  YES 
      * CPU microcode is known to cause stability problems:  NO  (model 0x9e family 0x6 stepping 0x9 ucode 0xc6 cpuid 0x906e9)
      * CPU microcode is the latest known available version:  YES  (latest version is 0xc6 dated 2019/08/14 according to builtin MCExtractor DB v130 - 2019/11/04)
    * CPU vulnerability to the speculative execution attack variants
      * Vulnerable to CVE-2017-5753 (Spectre Variant 1, bounds check bypass):  YES 
      * Vulnerable to CVE-2017-5715 (Spectre Variant 2, branch target injection):  YES 
      * Vulnerable to CVE-2017-5754 (Variant 3, Meltdown, rogue data cache load):  YES 
      * Vulnerable to CVE-2018-3640 (Variant 3a, rogue system register read):  YES 
      * Vulnerable to CVE-2018-3639 (Variant 4, speculative store bypass):  YES 
      * Vulnerable to CVE-2018-3615 (Foreshadow (SGX), L1 terminal fault):  YES 
      * Vulnerable to CVE-2018-3620 (Foreshadow-NG (OS), L1 terminal fault):  YES 
      * Vulnerable to CVE-2018-3646 (Foreshadow-NG (VMM), L1 terminal fault):  YES 
      * Vulnerable to CVE-2018-12126 (Fallout, microarchitectural store buffer data sampling (MSBDS)):  YES 
      * Vulnerable to CVE-2018-12130 (ZombieLoad, microarchitectural fill buffer data sampling (MFBDS)):  YES 
      * Vulnerable to CVE-2018-12127 (RIDL, microarchitectural load port data sampling (MLPDS)):  YES 
      * Vulnerable to CVE-2019-11091 (RIDL, microarchitectural data sampling uncacheable memory (MDSUM)):  YES 
      * Vulnerable to CVE-2019-11135 (Transactional Synchronization Extensions (TSX) Asynchronous Abort (TAA)):  NO 
    
    CVE-2017-5753 aka 'Spectre Variant 1, bounds check bypass'
    * Mitigated according to the /sys interface:  YES  (Mitigation: usercopy/swapgs barriers and __user pointer sanitization)
    * Kernel has array_index_mask_nospec:  UNKNOWN  (couldn't check (missing 'lzop' tool, please install it, usually it's in the 'lzop' package))
    * Kernel has the Red Hat/Ubuntu patch:  UNKNOWN  (couldn't check (missing 'lzop' tool, please install it, usually it's in the 'lzop' package))
    * Kernel has mask_nospec64 (arm64):  UNKNOWN  (couldn't check (missing 'lzop' tool, please install it, usually it's in the 'lzop' package))
    * Checking count of LFENCE instructions following a jump in kernel...  UNKNOWN  (couldn't check (missing 'lzop' tool, please install it, usually it's in the 'lzop' package))
    > STATUS:  NOT VULNERABLE  (Mitigation: usercopy/swapgs barriers and __user pointer sanitization)
    
    CVE-2017-5715 aka 'Spectre Variant 2, branch target injection'
    * Mitigated according to the /sys interface:  YES  (Mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling)
    * Mitigation 1
      * Kernel is compiled with IBRS support:  YES 
        * IBRS enabled and active:  YES  (for firmware code only)
      * Kernel is compiled with IBPB support:  YES 
        * IBPB enabled and active:  YES 
    * Mitigation 2
      * Kernel has branch predictor hardening (arm):  NO 
      * Kernel compiled with retpoline option:  YES 
        * Kernel compiled with a retpoline-aware compiler:  YES  (kernel reports full retpoline compilation)
      * Kernel supports RSB filling:  UNKNOWN  (couldn't check (missing 'lzop' tool, please install it, usually it's in the 'lzop' package))
    > STATUS:  VULNERABLE  (IBRS+IBPB or retpoline+IBPB+RSB filling, is needed to mitigate the vulnerability)
    
    CVE-2017-5754 aka 'Variant 3, Meltdown, rogue data cache load'
    * Mitigated according to the /sys interface:  YES  (Mitigation: PTI)
    * Kernel supports Page Table Isolation (PTI):  YES 
      * PTI enabled and active:  YES 
      * Reduced performance impact of PTI:  YES  (CPU supports INVPCID, performance impact of PTI will be greatly reduced)
    * Running as a Xen PV DomU:  NO 
    > STATUS:  NOT VULNERABLE  (Mitigation: PTI)
    
    CVE-2018-3640 aka 'Variant 3a, rogue system register read'
    * CPU microcode mitigates the vulnerability:  YES 
    > STATUS:  NOT VULNERABLE  (your CPU microcode mitigates the vulnerability)
    
    CVE-2018-3639 aka 'Variant 4, speculative store bypass'
    * Mitigated according to the /sys interface:  YES  (Mitigation: Speculative Store Bypass disabled via prctl and seccomp)
    * Kernel supports disabling speculative store bypass (SSB):  YES  (found in /proc/self/status)
    * SSB mitigation is enabled and active:  YES  (per-thread through prctl)
    * SSB mitigation currently active for selected processes:  YES  (boltd firefox fwupd geoclue irqbalance ModemManager pulseaudio systemd-journald systemd-logind systemd-resolved systemd-timesyncd systemd-udevd upowerd)
    > STATUS:  NOT VULNERABLE  (Mitigation: Speculative Store Bypass disabled via prctl and seccomp)
    
    CVE-2018-3615 aka 'Foreshadow (SGX), L1 terminal fault'
    * CPU microcode mitigates the vulnerability:  NO 
    > STATUS:  VULNERABLE  (your CPU supports SGX and the microcode is not up to date)
    
    CVE-2018-3620 aka 'Foreshadow-NG (OS), L1 terminal fault'
    * Mitigated according to the /sys interface:  YES  (Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable)
    * Kernel supports PTE inversion: strings: '': No such file
     NO 
    * PTE inversion enabled and active:  YES 
    > STATUS:  NOT VULNERABLE  (Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable)
    
    CVE-2018-3646 aka 'Foreshadow-NG (VMM), L1 terminal fault'
    * Information from the /sys interface: Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
    * This system is a host running a hypervisor:  NO 
    * Mitigation 1 (KVM)
      * EPT is disabled:  NO 
    * Mitigation 2
      * L1D flush is supported by kernel:  YES  (found flush_l1d in /proc/cpuinfo)
      * L1D flush enabled:  YES  (conditional flushes)
      * Hardware-backed L1D flush supported:  YES  (performance impact of the mitigation will be greatly reduced)
      * Hyper-Threading (SMT) is enabled:  YES 
    > STATUS:  NOT VULNERABLE  (this system is not running a hypervisor)
    
    CVE-2018-12126 aka 'Fallout, microarchitectural store buffer data sampling (MSBDS)'
    * Mitigated according to the /sys interface:  YES  (Mitigation: Clear CPU buffers; SMT vulnerable)
    * Kernel supports using MD_CLEAR mitigation:  YES  (md_clear found in /proc/cpuinfo)
    * Kernel mitigation is enabled and active:  YES 
    * SMT is either mitigated or disabled:  NO 
    > STATUS:  NOT VULNERABLE  (Your microcode and kernel are both up to date for this mitigation, and mitigation is enabled)
    
    CVE-2018-12130 aka 'ZombieLoad, microarchitectural fill buffer data sampling (MFBDS)'
    * Mitigated according to the /sys interface:  YES  (Mitigation: Clear CPU buffers; SMT vulnerable)
    * Kernel supports using MD_CLEAR mitigation:  YES  (md_clear found in /proc/cpuinfo)
    * Kernel mitigation is enabled and active:  YES 
    * SMT is either mitigated or disabled:  NO 
    > STATUS:  NOT VULNERABLE  (Your microcode and kernel are both up to date for this mitigation, and mitigation is enabled)
    
    CVE-2018-12127 aka 'RIDL, microarchitectural load port data sampling (MLPDS)'
    * Mitigated according to the /sys interface:  YES  (Mitigation: Clear CPU buffers; SMT vulnerable)
    * Kernel supports using MD_CLEAR mitigation:  YES  (md_clear found in /proc/cpuinfo)
    * Kernel mitigation is enabled and active:  YES 
    * SMT is either mitigated or disabled:  NO 
    > STATUS:  NOT VULNERABLE  (Your microcode and kernel are both up to date for this mitigation, and mitigation is enabled)
    
    CVE-2019-11091 aka 'RIDL, microarchitectural data sampling uncacheable memory (MDSUM)'
    * Mitigated according to the /sys interface:  YES  (Mitigation: Clear CPU buffers; SMT vulnerable)
    * Kernel supports using MD_CLEAR mitigation:  YES  (md_clear found in /proc/cpuinfo)
    * Kernel mitigation is enabled and active:  YES 
    * SMT is either mitigated or disabled:  NO 
    > STATUS:  NOT VULNERABLE  (Your microcode and kernel are both up to date for this mitigation, and mitigation is enabled)
    
    CVE-2019-11135 aka 'Transactional Synchronization Extensions (TSX) Asynchronous Abort (TAA)'
    * Mitigated according to the /sys interface:  YES  (Not affected)
    * TAA mitigation is supported by kernel:  UNKNOWN  (missing 'lzop' tool, please install it, usually it's in the 'lzop' package)
    * TAA mitigation enabled and active:  NO 
    > STATUS:  NOT VULNERABLE  (your CPU vendor reported your CPU model as not vulnerable)
    
    > SUMMARY: CVE-2017-5753:OK CVE-2017-5715:KO CVE-2017-5754:OK CVE-2018-3640:OK CVE-2018-3639:OK CVE-2018-3615:KO CVE-2018-3620:OK CVE-2018-3646:OK CVE-2018-12126:OK CVE-2018-12130:OK CVE-2018-12127:OK CVE-2019-11091:OK CVE-2019-11135:OK
    
    Need more detailed information about mitigation options? Use --explain
    A false sense of security is worse than no security at all, see --disclaimer
    corrado@corrado-p6-eoan-1017:~$
    Code:
    corrado@corrado-p5-disco:~$ date
    mer 13 nov 2019, 13:46:48, CET
    corrado@corrado-p5-disco:~$ 
    
    corrado@corrado-p5-disco:~$ sudo ./spectre-meltdown-checker.sh
    Spectre and Meltdown mitigation detection tool v0.42
    
    Checking for vulnerabilities on current system
    Kernel is Linux 5.0.0-32-generic #34-Ubuntu SMP Wed Oct 2 02:06:48 UTC 2019 x86_64
    CPU is Intel(R) Core(TM) i3-7100 CPU @ 3.90GHz
    
    Hardware check
    * Hardware support (CPU microcode) for mitigation techniques
      * Indirect Branch Restricted Speculation (IBRS)
        * SPEC_CTRL MSR is available:  YES 
        * CPU indicates IBRS capability:  YES  (SPEC_CTRL feature bit)
      * Indirect Branch Prediction Barrier (IBPB)
        * PRED_CMD MSR is available:  YES 
        * CPU indicates IBPB capability:  YES  (SPEC_CTRL feature bit)
      * Single Thread Indirect Branch Predictors (STIBP)
        * SPEC_CTRL MSR is available:  YES 
        * CPU indicates STIBP capability:  YES  (Intel STIBP feature bit)
      * Speculative Store Bypass Disable (SSBD)
        * CPU indicates SSBD capability:  YES  (Intel SSBD)
      * L1 data cache invalidation
        * FLUSH_CMD MSR is available:  YES 
        * CPU indicates L1D flush capability:  YES  (L1D flush feature bit)
      * Microarchitectural Data Sampling
        * VERW instruction is available:  YES  (MD_CLEAR feature bit)
      * TSX Asynchronous Abort
        * TSX support is available:  NO 
      * Enhanced IBRS (IBRS_ALL)
        * CPU indicates ARCH_CAPABILITIES MSR availability:  NO 
        * ARCH_CAPABILITIES MSR advertises IBRS_ALL capability:  NO 
      * CPU explicitly indicates not being vulnerable to Meltdown/L1TF (RDCL_NO):  NO 
      * CPU explicitly indicates not being vulnerable to Variant 4 (SSB_NO):  NO 
      * CPU/Hypervisor indicates L1D flushing is not necessary on this system:  NO 
      * Hypervisor indicates host CPU might be vulnerable to RSB underflow (RSBA):  NO 
      * CPU explicitly indicates not being vulnerable to Microarchitectural Data Sampling (MDS_NO):  NO 
      * CPU explicitly indicates not being vulnerable to TSX Asynchrnonous Abort (TAA_NO):  NO 
      * CPU supports Software Guard Extensions (SGX):  YES 
      * CPU microcode is known to cause stability problems:  NO  (model 0x9e family 0x6 stepping 0x9 ucode 0xb4 cpuid 0x906e9)
      * CPU microcode is the latest known available version:  NO  (latest version is 0xc6 dated 2019/08/14 according to builtin MCExtractor DB v130 - 2019/11/04)
    * CPU vulnerability to the speculative execution attack variants
      * Vulnerable to CVE-2017-5753 (Spectre Variant 1, bounds check bypass):  YES 
      * Vulnerable to CVE-2017-5715 (Spectre Variant 2, branch target injection):  YES 
      * Vulnerable to CVE-2017-5754 (Variant 3, Meltdown, rogue data cache load):  YES 
      * Vulnerable to CVE-2018-3640 (Variant 3a, rogue system register read):  YES 
      * Vulnerable to CVE-2018-3639 (Variant 4, speculative store bypass):  YES 
      * Vulnerable to CVE-2018-3615 (Foreshadow (SGX), L1 terminal fault):  YES 
      * Vulnerable to CVE-2018-3620 (Foreshadow-NG (OS), L1 terminal fault):  YES 
      * Vulnerable to CVE-2018-3646 (Foreshadow-NG (VMM), L1 terminal fault):  YES 
      * Vulnerable to CVE-2018-12126 (Fallout, microarchitectural store buffer data sampling (MSBDS)):  YES 
      * Vulnerable to CVE-2018-12130 (ZombieLoad, microarchitectural fill buffer data sampling (MFBDS)):  YES 
      * Vulnerable to CVE-2018-12127 (RIDL, microarchitectural load port data sampling (MLPDS)):  YES 
      * Vulnerable to CVE-2019-11091 (RIDL, microarchitectural data sampling uncacheable memory (MDSUM)):  YES 
      * Vulnerable to CVE-2019-11135 (Transactional Synchronization Extensions (TSX) Asynchronous Abort (TAA)):  NO 
    
    CVE-2017-5753 aka 'Spectre Variant 1, bounds check bypass'
    * Mitigated according to the /sys interface:  YES  (Mitigation: usercopy/swapgs barriers and __user pointer sanitization)
    * Kernel has array_index_mask_nospec:  YES  (1 occurrence(s) found of x86 64 bits array_index_mask_nospec())
    * Kernel has the Red Hat/Ubuntu patch:  NO 
    * Kernel has mask_nospec64 (arm64):  NO 
    > STATUS:  NOT VULNERABLE  (Mitigation: usercopy/swapgs barriers and __user pointer sanitization)
    
    CVE-2017-5715 aka 'Spectre Variant 2, branch target injection'
    * Mitigated according to the /sys interface:  YES  (Mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling)
    * Mitigation 1
      * Kernel is compiled with IBRS support:  YES 
        * IBRS enabled and active:  YES  (for firmware code only)
      * Kernel is compiled with IBPB support:  YES 
        * IBPB enabled and active:  YES 
    * Mitigation 2
      * Kernel has branch predictor hardening (arm):  NO 
      * Kernel compiled with retpoline option:  YES 
        * Kernel compiled with a retpoline-aware compiler:  YES  (kernel reports full retpoline compilation)
      * Kernel supports RSB filling:  YES 
    > STATUS:  NOT VULNERABLE  (Full retpoline + IBPB are mitigating the vulnerability)
    
    CVE-2017-5754 aka 'Variant 3, Meltdown, rogue data cache load'
    * Mitigated according to the /sys interface:  YES  (Mitigation: PTI)
    * Kernel supports Page Table Isolation (PTI):  YES 
      * PTI enabled and active:  YES 
      * Reduced performance impact of PTI:  YES  (CPU supports INVPCID, performance impact of PTI will be greatly reduced)
    * Running as a Xen PV DomU:  NO 
    > STATUS:  NOT VULNERABLE  (Mitigation: PTI)
    
    CVE-2018-3640 aka 'Variant 3a, rogue system register read'
    * CPU microcode mitigates the vulnerability:  YES 
    > STATUS:  NOT VULNERABLE  (your CPU microcode mitigates the vulnerability)
    
    CVE-2018-3639 aka 'Variant 4, speculative store bypass'
    * Mitigated according to the /sys interface:  YES  (Mitigation: Speculative Store Bypass disabled via prctl and seccomp)
    * Kernel supports disabling speculative store bypass (SSB):  YES  (found in /proc/self/status)
    * SSB mitigation is enabled and active:  YES  (per-thread through prctl)
    * SSB mitigation currently active for selected processes:  YES  (boltd firefox fwupd geoclue irqbalance ModemManager systemd-journald systemd-logind systemd-resolved systemd-timesyncd systemd-udevd upowerd)
    > STATUS:  NOT VULNERABLE  (Mitigation: Speculative Store Bypass disabled via prctl and seccomp)
    
    CVE-2018-3615 aka 'Foreshadow (SGX), L1 terminal fault'
    * CPU microcode mitigates the vulnerability:  YES 
    > STATUS:  NOT VULNERABLE  (your CPU microcode mitigates the vulnerability)
    
    CVE-2018-3620 aka 'Foreshadow-NG (OS), L1 terminal fault'
    * Mitigated according to the /sys interface:  YES  (Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable)
    * Kernel supports PTE inversion:  YES  (found in kernel image)
    * PTE inversion enabled and active:  YES 
    > STATUS:  NOT VULNERABLE  (Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable)
    
    CVE-2018-3646 aka 'Foreshadow-NG (VMM), L1 terminal fault'
    * Information from the /sys interface: Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
    * This system is a host running a hypervisor:  NO 
    * Mitigation 1 (KVM)
      * EPT is disabled:  NO 
    * Mitigation 2
      * L1D flush is supported by kernel:  YES  (found flush_l1d in /proc/cpuinfo)
      * L1D flush enabled:  YES  (conditional flushes)
      * Hardware-backed L1D flush supported:  YES  (performance impact of the mitigation will be greatly reduced)
      * Hyper-Threading (SMT) is enabled:  YES 
    > STATUS:  NOT VULNERABLE  (this system is not running a hypervisor)
    
    CVE-2018-12126 aka 'Fallout, microarchitectural store buffer data sampling (MSBDS)'
    * Mitigated according to the /sys interface:  YES  (Mitigation: Clear CPU buffers; SMT vulnerable)
    * Kernel supports using MD_CLEAR mitigation:  YES  (md_clear found in /proc/cpuinfo)
    * Kernel mitigation is enabled and active:  YES 
    * SMT is either mitigated or disabled:  NO 
    > STATUS:  NOT VULNERABLE  (Your microcode and kernel are both up to date for this mitigation, and mitigation is enabled)
    
    CVE-2018-12130 aka 'ZombieLoad, microarchitectural fill buffer data sampling (MFBDS)'
    * Mitigated according to the /sys interface:  YES  (Mitigation: Clear CPU buffers; SMT vulnerable)
    * Kernel supports using MD_CLEAR mitigation:  YES  (md_clear found in /proc/cpuinfo)
    * Kernel mitigation is enabled and active:  YES 
    * SMT is either mitigated or disabled:  NO 
    > STATUS:  NOT VULNERABLE  (Your microcode and kernel are both up to date for this mitigation, and mitigation is enabled)
    
    CVE-2018-12127 aka 'RIDL, microarchitectural load port data sampling (MLPDS)'
    * Mitigated according to the /sys interface:  YES  (Mitigation: Clear CPU buffers; SMT vulnerable)
    * Kernel supports using MD_CLEAR mitigation:  YES  (md_clear found in /proc/cpuinfo)
    * Kernel mitigation is enabled and active:  YES 
    * SMT is either mitigated or disabled:  NO 
    > STATUS:  NOT VULNERABLE  (Your microcode and kernel are both up to date for this mitigation, and mitigation is enabled)
    
    CVE-2019-11091 aka 'RIDL, microarchitectural data sampling uncacheable memory (MDSUM)'
    * Mitigated according to the /sys interface:  YES  (Mitigation: Clear CPU buffers; SMT vulnerable)
    * Kernel supports using MD_CLEAR mitigation:  YES  (md_clear found in /proc/cpuinfo)
    * Kernel mitigation is enabled and active:  YES 
    * SMT is either mitigated or disabled:  NO 
    > STATUS:  NOT VULNERABLE  (Your microcode and kernel are both up to date for this mitigation, and mitigation is enabled)
    
    CVE-2019-11135 aka 'Transactional Synchronization Extensions (TSX) Asynchronous Abort (TAA)'
    * TAA mitigation is supported by kernel:  NO 
    * TAA mitigation enabled and active:  NO  (tsx_async_abort not found in sysfs hierarchy)
    > STATUS:  NOT VULNERABLE  (your CPU vendor reported your CPU model as not vulnerable)
    
    > SUMMARY: CVE-2017-5753:OK CVE-2017-5715:OK CVE-2017-5754:OK CVE-2018-3640:OK CVE-2018-3639:OK CVE-2018-3615:OK CVE-2018-3620:OK CVE-2018-3646:OK CVE-2018-12126:OK CVE-2018-12130:OK CVE-2018-12127:OK CVE-2019-11091:OK CVE-2019-11135:OK
    
    Need more detailed information about mitigation options? Use --explain
    A false sense of security is worse than no security at all, see --disclaimer
    corrado@corrado-p5-disco:~$
    Opened a problem on github: https://github.com/speed47/spectre-m...ker/issues/316
    script has been updated, it was a false positive.
    Last edited by corradoventu; 2 Weeks Ago at 08:27 AM.

Page 22 of 22 FirstFirst ... 12202122

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •