Lscpu shows AMD 5950x as Vulnerable to Spectre Variant 4

Spectre Variant 4 a.k.a. “Speculative Store Bypass” is showing as vulnerable and not mitigated on my new system. Here is the info:

  • Windows 10 Host
  • 5950x

I’ve checked in a linux VM and in WSL and in both places when I use lscpu the vulnerability is shown as not mitigated. Any ideas as to why? I’ve updated drivers and BIOS so I’m not sure why it’s not.

Here is lscpu output:

derek@derek-VirtualBox:~$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 48 bits physical, 48 bits virtual
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: AuthenticAMD
CPU family: 25
Model: 33
Model name: AMD Ryzen 9 5950X 16-Core Processor
Stepping: 0
CPU MHz: 3393.620
BogoMIPS: 6787.24
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 128 KiB
L1i cache: 128 KiB
L2 cache: 2 MiB
L3 cache: 64 MiB
NUMA node0 CPU(s): 0-3
Vulnerability Itlb multihit: Not affected
Vulnerability L1tf: Not affected
Vulnerability Mds: Not affected
Vulnerability Meltdown: Not affected
Vulnerability Spec store bypass: Vulnerable
Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __use
r pointer sanitization
Vulnerability Spectre v2: Mitigation; Full AMD retpoline, STIBP disabled
, RSB filling
Vulnerability Srbds: Not affected
Vulnerability Tsx async abort: Not affected
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mt
rr pge mca cmov pat pse36 clflush mmx fxsr sse
sse2 ht syscall nx fxsr_opt rdtscp lm constan
t_tsc rep_good nopl nonstop_tsc cpuid extd_api
cid tsc_known_freq pni ssse3 sse4_1 sse4_2 hyp
ervisor lahf_lm cmp_legacy cr8_legacy 3dnowpre
fetch vmmcall fsgsbase arat

I am guessing it is because it would be unlikely to be exploited against a home users hardware and the mitigations are too severe on performance.

1 Like

That makes sense. I wish I could find somewhere in AMD documentation that states they turn this off by default on consumer processors. I wonder if the Threadripper PRO cpu’s will have this feature enabled.

This topic was automatically closed 273 days after the last reply. New replies are no longer allowed.