mirror of
https://github.com/speed47/spectre-meltdown-checker
synced 2024-11-19 04:22:22 +01:00
cleanup: remove superseded atom detection code
This is now handled properly by checking the CPU vendor, family, model instead of looking for the commercial name of the CPU in /proc/cpuinfo
This commit is contained in:
parent
247b176882
commit
0267659adc
@ -210,19 +210,10 @@ is_cpu_vulnerable()
|
|||||||
variant3=immune
|
variant3=immune
|
||||||
elif [ "$cpu_vendor" = GenuineIntel ]; then
|
elif [ "$cpu_vendor" = GenuineIntel ]; then
|
||||||
# Intel
|
# Intel
|
||||||
# Old Atoms are not vulnerable to spectre 2 nor meltdown
|
|
||||||
# https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00088&languageid=en-fr
|
|
||||||
# model name : Genuine Intel(R) CPU N270 @ 1.60GHz
|
|
||||||
# model name : Intel(R) Atom(TM) CPU N270 @ 1.60GHz
|
|
||||||
# model name : Intel(R) Atom(TM) CPU 330 @ 1.60GHz
|
|
||||||
if grep -qE '^model name.+ Intel\(R\) (Atom\(TM\) CPU +(S|D|N|230|330)|CPU N[0-9]{3} )' /proc/cpuinfo; then
|
|
||||||
variant1=vuln
|
|
||||||
[ -z "$variant2" ] && variant2=immune
|
|
||||||
[ -z "$variant3" ] && variant3=immune
|
|
||||||
# https://github.com/crozone/SpectrePoC/issues/1 ^F E5200 => spectre 2 not vulnerable
|
# https://github.com/crozone/SpectrePoC/issues/1 ^F E5200 => spectre 2 not vulnerable
|
||||||
# https://github.com/paboldin/meltdown-exploit/issues/19 ^F E5200 => meltdown vulnerable
|
# https://github.com/paboldin/meltdown-exploit/issues/19 ^F E5200 => meltdown vulnerable
|
||||||
# model name : Pentium(R) Dual-Core CPU E5200 @ 2.50GHz
|
# model name : Pentium(R) Dual-Core CPU E5200 @ 2.50GHz
|
||||||
elif grep -qE '^model name.+ Pentium\(R\) Dual-Core[[:space:]]+CPU[[:space:]]+E[0-9]{4}K? ' /proc/cpuinfo; then
|
if grep -qE '^model name.+ Pentium\(R\) Dual-Core[[:space:]]+CPU[[:space:]]+E[0-9]{4}K? ' /proc/cpuinfo; then
|
||||||
variant1=vuln
|
variant1=vuln
|
||||||
[ -z "$variant2" ] && variant2=immune
|
[ -z "$variant2" ] && variant2=immune
|
||||||
variant3=vuln
|
variant3=vuln
|
||||||
|
Loading…
Reference in New Issue
Block a user