Today article is in keeping with a theme...

[KGIII]

It's an article that covers the 'lscpu' command, or the command that'll hopefully show you some information about your CPU.

A Little About The 'lscpu' Command • Linux Tips

In today's article we're going to do what the title says, we're going to learn a little about the 'lscpu' command.

linux-tips.us

I do love me some feedback.

 

[Terminal Velocity]

This is my machina:
What about those vulnerabilities?
And is it safe to publish my vulnerabilities publicly?

Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
Address sizes:                   43 bits physical, 48 bits virtual
CPU(s):                          2
On-line CPU(s) list:             0,1
Thread(s) per core:              1
Core(s) per socket:              2
Socket(s):                       1
NUMA node(s):                    1
Vendor ID:                       AuthenticAMD
CPU family:                      23
Model:                           32
Model name:                      AMD 3020e with Radeon Graphics
Stepping:                        1
Frequency boost:                 enabled
CPU MHz:                         731.541
CPU max MHz:                     1200,0000
CPU min MHz:                     800,0000
BogoMIPS:                        2395.48
Virtualization:                  AMD-V
L1d cache:                       64 KiB
L1i cache:                       128 KiB
L2 cache:                        1 MiB
L3 cache:                        4 MiB
NUMA node0 CPU(s):               0,1
Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Mmio stale data:   Not affected
Vulnerability Retbleed:          Mitigation; untrained return thunk; SMT disabled
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled                                                     via prctl and seccomp
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and                                                            __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Retpolines, IBPB conditional, STIBP
                                               disabled, RSB filling, PBRSB-eIBRS Not affected
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected

 

[KGIII]

What about those vulnerabilities?

There were some generations of CPUs affected by some malware, like Meltdown and Spectre. Your CPU does not appear to be vulnerable.

And is it safe to publish my vulnerabilities publicly?

You should be just fine.

Kinda amusingly, the CPUs that have those vulnerabilities have fixes in the code and those fixes slow down the CPUs. It's not a huge amount but the real world performance of a 4.5 GHz CPU might be closer to like 4.4 GHz.

It's actually possible to turn those protections off. I have how to do so in my notes, so they may someday become another article - one of those 'this is probably a bad idea' type of articles that I kinda enjoy.