add kernel version information to the output

fix(centos): check according to redhat patch.

README.md

@@ -5,28 +5,34 @@ A simple shell script to tell if your Linux installation is vulnerable
 against the 3 "speculative execution" CVEs:
 
 CVE-2017-5753 bounds check bypass (Spectre Variant 1)
-   Impact: Kernel & all software
+
-   Mitigation: recompile software *and* kernel with a modified compiler that introduces the LFENCE opcode at the proper positions in the resulting code
+   - Impact: Kernel & all software
-   Performance impact of the mitigation: negligible
+   - Mitigation: recompile software *and* kernel with a modified compiler that introduces the LFENCE opcode at the proper positions in the resulting code
+   - Performance impact of the mitigation: negligible
 
 CVE-2017-5715: branch target injection (Spectre Variant 2)
-   Impact: Kernel
+
-   Mitigation 1: new opcode via microcode update that should be used by up to date compilers to protect the BTB (by flushing indirect branch predictors)
+   - Impact: Kernel
-   Mitigation 2: introducing "retpoline" into compilers, and recompile software/OS with it
+   - Mitigation 1: new opcode via microcode update that should be used by up to date compilers to protect the BTB (by flushing indirect branch predictors)
-   Performance impact of the mitigation: high for mitigation 1, medium for mitigation 2, depending on your CPU
+   - Mitigation 2: introducing "retpoline" into compilers, and recompile software/OS with it
+   - Performance impact of the mitigation: high for mitigation 1, medium for mitigation 2, depending on your CPU
 
 CVE-2017-5754: rogue data cache load (Meltdown)
-   Impact: Kernel
+
-   Mitigation: updated kernel (with PTI/KPTI patches), updating the kernel is enough
+   - Impact: Kernel
-   Performance impact of the mitigation: low to medium
+   - Mitigation: updated kernel (with PTI/KPTI patches), updating the kernel is enough
+   - Performance impact of the mitigation: low to medium
 
 Example of the output of the script:
 
-Spectre and Meltdown mitigation detection tool v0.01
+
+```
+$ sudo ./spectre-meltdown-checker.sh
+Spectre and Meltdown mitigation detection tool v0.07
 
 CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1'
-* Kernel recompiled with LFENCE opcode insertion: UNKNOWN (check not yet implemented)
+* Kernel compiled with LFENCE opcode inserted at the proper places:  NO  (only 38 opcodes found, should be >= 60)
-> STATUS: UNKNOWN (not implemented, but real answer is most probably VULNERABLE at this stage)
+> STATUS:  VULNERABLE
 
 CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
 * Mitigation 1
@@ -35,10 +41,11 @@ CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
 *   IBRS enabled for Kernel space:  NO
 *   IBRS enabled for User space:  NO
 * Mitigation 2
-*   Kernel recompiled with retpoline: UNKNOWN (check not yet implemented)
+*   Kernel compiled with retpolines:  NO
-> STATUS: VULNERABLE (IBRS hardware + kernel support OR retpoline-compiled kernel are needed to mitigate the vulnerability)
+> STATUS:  VULNERABLE  (IBRS hardware + kernel support OR kernel with retpolines are needed to mitigate the vulnerability)
 
 CVE-2017-5754 [rogue data cache load] aka 'Meltdown' aka 'Variant 3'
 * Kernel supports Page Table Isolation (PTI):  YES
 * PTI enabled and active:  YES
 > STATUS:  NOT VULNERABLE  (PTI mitigates the vulnerability)
+```

spectre-meltdown-checker.sh

@@ -1,8 +1,9 @@
 #! /bin/sh
 # Spectre & Meltdown checker
-# Stephane Lesimple, v0.00.01
+# Stephane Lesimple
-VERSION=0.01
+VERSION=0.12
 
+# print status function
 pstatus()
 {
 	case "$1" in
@@ -11,60 +12,175 @@ pstatus()
 		yellow) col="\033[103m\033[30m";;
 		*)      col="";;
 	esac
-	echo -n "$col$2\033[0m"
+	/bin/echo -ne "$col $2 \033[0m"
-	[ -n "$3" ] && echo -n " ($3)"
+	[ -n "$3" ] && /bin/echo -n " ($3)"
-	echo
+	/bin/echo
 }
 
-echo "Spectre and Meltdown mitigation detection tool v$VERSION"
+# The 3 below functions are taken from the extract-linux script, available here:
-echo
+# https://github.com/torvalds/linux/blob/master/scripts/extract-vmlinux
+# The functions have been modified for better integration to this script
+# The original header of the file has been retained below
 
+# ----------------------------------------------------------------------
+# extract-vmlinux - Extract uncompressed vmlinux from a kernel image
+#
+# Inspired from extract-ikconfig
+# (c) 2009,2010 Dick Streefland <dick@streefland.net>
+#
+# (c) 2011      Corentin Chary <corentin.chary@gmail.com>
+#
+# Licensed under the GNU General Public License, version 2 (GPLv2).
+# ----------------------------------------------------------------------
+
+check_vmlinux()
+{
+	file "$1" 2>/dev/null | grep -q ELF || return 1
+	return 0
+}
+
+try_decompress()
+{
+        # The obscure use of the "tr" filter is to work around older versions of
+        # "grep" that report the byte offset of the line instead of the pattern.
+
+        # Try to find the header ($1) and decompress from here
+        for     pos in `tr "$1\n$2" "\n$2=" < "$4" | grep -abo "^$2"`
+        do
+                pos=${pos%%:*}
+                tail -c+$pos "$4" | $3 > $vmlinuxtmp 2> /dev/null
+                check_vmlinux "$vmlinuxtmp" && echo "$vmlinuxtmp" && return 0
+        done
+	return 1
+}
+
+extract_vmlinux()
+{
+	[ -n "$1" ] || return 1
+	# Prepare temp files:
+	vmlinuxtmp="$(mktemp /tmp/vmlinux-XXX)"
+
+	# Initial attempt for uncompressed images or objects:
+	if check_vmlinux "$1"; then
+		cat "$1" > "$vmlinuxtmp"
+		echo "$vmlinuxtmp"
+		return 0
+	fi
+
+	# That didn't work, so retry after decompression.
+	try_decompress '\037\213\010' xy    gunzip     "$1" && return 0
+	try_decompress '\3757zXZ\000' abcde unxz       "$1" && return 0
+	try_decompress 'BZh'          xy    bunzip2    "$1" && return 0
+	try_decompress '\135\0\0\0'   xxx   unlzma     "$1" && return 0
+	try_decompress '\211\114\132' xy    'lzop -d'  "$1" && return 0
+	return 1
+}
+
+# end of extract-vmlinux functions
+
+/bin/echo -e "\033[1;34mSpectre and Meltdown mitigation detection tool v$VERSION\033[0m"
+/bin/echo
+
+# root check
+
+if [ "$(id -u)" -ne 0 ]; then
+	/bin/echo -e "\033[31mNote that you should launch this script with root privileges to get accurate information.\033[0m"
+	/bin/echo -e "\033[31mWe'll proceed but you might see permission denied errors.\033[0m"
+	/bin/echo -e "\033[31mTo run it as root, you can try the following command: sudo $0\033[0m"
+	/bin/echo
+fi
+
+/bin/echo -e "Checking vulnerabilities against \033[35m"$(uname -s) $(uname -r) $(uname -m)"\033[0m"
+/bin/echo
+
+###########
 # SPECTRE 1
-echo "\033[1;34mCVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1'\033[0m"
+/bin/echo -e "\033[1;34mCVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1'\033[0m"
-echo -n "* Kernel recompiled with LFENCE opcode insertion: "
+/bin/echo -n "* Kernel compiled with LFENCE opcode inserted at the proper places: "
-pstatus yellow UNKNOWN "check not yet implemented"
-echo -n "> \033[46m\033[30mSTATUS:\033[0m "
-pstatus yellow UNKNOWN "not implemented, but real answer is most probably VULNERABLE at this stage"
 
+status=0
+img=''
+# try to find the image of the current running kernel
+[ -e /boot/vmlinuz-linux       ] && img=/boot/vmlinuz-linux
+[ -e /boot/vmlinuz-$(uname -r) ] && img=/boot/vmlinuz-$(uname -r)
+[ -e /boot/kernel-$( uname -r) ] && img=/boot/kernel-$( uname -r)
+[ -e /boot/bzImage-$(uname -r) ] && img=/boot/bzImage-$(uname -r)
+[ -e /boot/kernel-genkernel-$(uname -m)-$(uname -r) ] && img=/boot/kernel-genkernel-$(uname -m)-$(uname -r)
+if [ -z "$img" ]; then
+	pstatus yellow UNKNOWN "couldn't find your kernel image in /boot, if you used netboot, this is normal"
+else
+	vmlinux=$(extract_vmlinux $img)
+	if [ -z "$vmlinux" -o ! -r "$vmlinux" ]; then
+		pstatus yellow UNKNOWN "couldn't extract your kernel from $img"
+	elif ! which objdump >/dev/null 2>&1; then
+		pstatus yellow UNKNOWN "missing 'objdump' tool, please install it, usually it's in the binutils package"
+	else
+		# here we disassemble the kernel and count the number of occurences of the LFENCE opcode
+		# in non-patched kernels, this has been empirically determined as being around 40-50
+		# in patched kernels, this is more around 70-80
+		nb_lfence=$(objdump -D "$vmlinux" | grep -wc lfence)
+		if [ "$nb_lfence" -lt 60 ]; then
+			pstatus red NO "only $nb_lfence opcodes found, should be >= 60"
+			status=1
+		else
+			pstatus green YES "$nb_lfence opcodes found, which is >= 60"
+			status=2
+		fi
+	fi
+fi
 
+/bin/echo -ne "> \033[46m\033[30mSTATUS:\033[0m "
+[ "$status" = 0 ] && pstatus yellow UNKNOWN
+[ "$status" = 1 ] && pstatus red VULNERABLE
+[ "$status" = 2 ] && pstatus green 'NOT VULNERABLE'
+
+###########
 # VARIANT 2
-echo
+/bin/echo
-echo "\033[1;34mCVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'\033[0m"
+/bin/echo -e "\033[1;34mCVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'\033[0m"
-echo "* Mitigation 1"
+/bin/echo "* Mitigation 1"
-echo -n "*   Hardware (CPU microcode) support for mitigation: "
+/bin/echo -n "*   Hardware (CPU microcode) support for mitigation: "
 if [ ! -e /dev/cpu/0/msr ]; then
+	# try to load the module ourselves (and remember it so we can rmmod it afterwards)
 	modprobe msr 2>/dev/null && insmod_msr=1
 fi
 if [ ! -e /dev/cpu/0/msr ]; then
 	pstatus yellow UNKNOWN "couldn't read /dev/cpu/0/msr, is msr support enabled in your kernel?"
 else
-	dd if=/dev/cpu/0/msr of=/dev/null bs=1 count=8 skip=72 2>/dev/null
+	# the new MSR 'SPEC_CTRL' is at offset 0x48
+	# here we use dd, it's the same as using 'rdmsr 0x48' but without needing the rdmsr tool
+	# if we get a read error, the MSR is not there
+	dd if=/dev/cpu/0/msr of=/dev/null bs=8 count=1 skip=9 2>/dev/null
 	if [ $? -eq 0 ]; then
 		pstatus green YES
 	else
 		pstatus red NO
 	fi
-	#dd if=/dev/cpu/0/msr of=/dev/null bs=1 count=8 skip=73 2>/dev/null
-	#echo $?
 fi
 
 if [ "$insmod_msr" = 1 ]; then
+	# if we used modprobe ourselves, rmmod the module
 	rmmod msr 2>/dev/null
 fi
 
-echo -n "*   Kernel support for IBRS: "
+/bin/echo -n "*   Kernel support for IBRS: "
 if [ -e /sys/kernel/debug/sched_features ]; then
+	# try to mount the debugfs hierarchy ourselves and remember it to umount afterwards
 	mount -t debugfs debugfs /sys/kernel/debug 2>/dev/null && mounted_debugfs=1
 fi
-if [ -e /sys/kernel/debug/ibrs_enabled ]; then
+if [ -e /sys/kernel/debug/ibrs_enabled -o -e /sys/kernel/debug/x86/ibrs_enabled ]; then
+	# if the file is there, we have IBRS compiled-in
 	pstatus green YES
 	ibrs_supported=1
 else
 	pstatus red NO
 fi
 
-ibrs_enabled=$(cat /sys/kernel/debug/ibrs_enabled 2>/dev/null)
+[ -f /sys/kernel/debug/ibrs_enabled ] && ibrs_enabled=$(cat /sys/kernel/debug/ibrs_enabled 2>/dev/null) || ibrs_enabled=$(cat /sys/kernel/debug/x86/ibrs_enabled 2>/dev/null)
-echo -n "*   IBRS enabled for Kernel space: "
+/bin/echo -n "*   IBRS enabled for Kernel space: "
+# 0 means disabled
+# 1 is enabled only for kernel space
+# 2 is enabled for kernel and user space
 case "$ibrs_enabled" in
 	"") [ "$ibrs_supported" = 1 ] && pstatus yellow UNKNOWN || pstatus red NO;;
 	0)     pstatus red NO;;
@@ -72,7 +188,7 @@ case "$ibrs_enabled" in
 	*)     pstatus yellow UNKNOWN;;
 esac
 
-echo -n "*   IBRS enabled for User space: "
+/bin/echo -n "*   IBRS enabled for User space: "
 case "$ibrs_enabled" in
 	"") [ "$ibrs_supported" = 1 ] && pstatus yellow UNKNOWN || pstatus red NO;;
 	0 | 1) pstatus red NO;;
@@ -81,56 +197,108 @@ case "$ibrs_enabled" in
 esac
 
 if [ "$mounted_debugfs" = 1 ]; then
+	# umount debugfs if we did mount it ourselves
 	umount /sys/kernel/debug
 fi
 
-echo "* Mitigation 2"
+/bin/echo "* Mitigation 2"
-echo -n "*   Kernel recompiled with retpoline: "
+/bin/echo -n "*   Kernel compiled with retpolines: "
-pstatus yellow UNKNOWN "check not yet implemented"
+# We check the RETPOLINE kernel options
-
+# XXX this doesn't mean the kernel has been compiled with a retpoline-aware gcc
-echo -n "> \033[46m\033[30mSTATUS:\033[0m "
+# still looking for a way do detect that ...
-if grep -q AMD /proc/cpuinfo; then
-	pstatus green "NOT VULNERABLE" "your CPU is not vulnerable as per the vendor"
-elif [ "$ibrs_enabled" = 1 -o "$ibrs_enabled" = 2 ]; then
-	pstatus green "NOT VULNERABLE" "IBRS mitigates the vulnerability"
-else
-	pstatus red VULNERABLE "IBRS hardware + kernel support OR retpoline-compiled kernel are needed to mitigate the vulnerability"
-fi
-
-# MELTDOWN
-echo
-echo "\033[1;34mCVE-2017-5754 [rogue data cache load] aka 'Meltdown' aka 'Variant 3'\033[0m"
-echo -n "* Kernel supports Page Table Isolation (PTI): "
 if [ -e /proc/config.gz ]; then
-	if zgrep -q '^CONFIG_PAGE_TABLE_ISOLATION=y' /proc/config.gz; then
+	# either the running kernel exports his own config
+	if zgrep -q '^CONFIG_RETPOLINE=y' /proc/config.gz; then
 		pstatus green YES
-		kpti_support=1
+		retpoline=1
 	else
 		pstatus red NO
 	fi
 elif [ -e /boot/config-$(uname -r) ]; then
-	if grep  -q '^CONFIG_PAGE_TABLE_ISOLATION=y' /boot/config-$(uname -r); then
+	# or we can find a config file in /root with the kernel release name
+	if grep  -q '^CONFIG_RETPOLINE=y' /boot/config-$(uname -r); then
 		pstatus green YES
-		kpti_support=1
+		retpoline=1
 	else
 		pstatus red NO
 	fi
 else
-	pstatus yellow UNKNOWN
+	pstatus yellow UNKNOWN "couldn't read your kernel configuration"
 fi
 
-echo -n "* PTI enabled and active: "
+/bin/echo -ne "> \033[46m\033[30mSTATUS:\033[0m "
+if grep -q AMD /proc/cpuinfo; then
+	pstatus green "NOT VULNERABLE" "your CPU is not vulnerable as per the vendor"
+elif [ "$ibrs_enabled" = 1 -o "$ibrs_enabled" = 2 ]; then
+	pstatus green "NOT VULNERABLE" "IBRS mitigates the vulnerability"
+elif [ "$retpoline" = 1 ]; then
+	pstatus green "NOT VULNERABLE" "retpolines mitigate the vulnerability"
+else
+	pstatus red VULNERABLE "IBRS hardware + kernel support OR kernel with retpolines are needed to mitigate the vulnerability"
+fi
+
+##########
+# MELTDOWN
+/bin/echo
+/bin/echo -e "\033[1;34mCVE-2017-5754 [rogue data cache load] aka 'Meltdown' aka 'Variant 3'\033[0m"
+/bin/echo -n "* Kernel supports Page Table Isolation (PTI): "
+kpti_support=0
+kpti_can_tell=0
+if [ -e /proc/config.gz ]; then
+	# either the running kernel exports his own config
+	kpti_can_tell=1
+	if zgrep -q '^CONFIG_PAGE_TABLE_ISOLATION=y' /proc/config.gz; then
+		kpti_support=1
+	fi
+elif [ -e /boot/config-$(uname -r) ]; then
+	# or we can find a config file in /root with the kernel release name
+	kpti_can_tell=1
+	if grep  -q '^CONFIG_PAGE_TABLE_ISOLATION=y' /boot/config-$(uname -r); then
+		kpti_support=1
+	fi
+fi
+if [ -e /boot/System.map-$(uname -r) ]; then
+	# it's not an elif: some backports don't have the PTI config but still include the patch
+	# so we try to find an exported symbol that is part of the PTI patch in System.map
+	kpti_can_tell=1
+	if grep -qw kpti_force_enabled /boot/System.map-$(uname -r); then
+		kpti_support=1
+	fi
+fi
+if [ -n "$vmlinux" ]; then
+	# same as above but in case we don't have System.map and only vmlinux, look for the
+	# nopti option that is part of the patch (kernel command line option)
+	kpti_can_tell=1
+	if strings "$vmlinux" | grep -qw nopti; then
+		kpti_support=1
+	fi
+fi
+
+if [ "$kpti_support" = 1 ]; then
+	pstatus green YES
+elif [ "$kpti_can_tell" = 1 ]; then
+	pstatus red NO
+else
+	pstatus yellow UNKNOWN "couldn't read your kernel configuration"
+fi
+
+/bin/echo -n "* PTI enabled and active: "
 if grep ^flags /proc/cpuinfo | grep -qw pti; then
+	# vanilla PTI patch sets the 'pti' flag in cpuinfo
 	pstatus green YES
 	kpti_enabled=1
-elif dmesg | grep -q 'Kernel/User page tables isolation: enabled'; then
+elif dmesg | grep -Eq 'Kernel/User page tables isolation: enabled|Kernel page table isolation enabled'; then
+	# if we can't find the flag, grep in dmesg
+	pstatus green YES
+	kpti_enabled=1
+elif [ -e /sys/kernel/debug/x86/pti_enabled -a "$(cat /sys/kernel/debug/x86/pti_enabled)" = 1 ]; then
 	pstatus green YES
 	kpti_enabled=1
 else
 	pstatus red NO
 fi
 
-echo -n "> \033[46m\033[30mSTATUS:\033[0m "
+/bin/echo -ne "> \033[46m\033[30mSTATUS:\033[0m "
 if grep -q AMD /proc/cpuinfo; then
 	pstatus green "NOT VULNERABLE" "your CPU is not vulnerable as per the vendor"
 elif [ "$kpti_enabled" = 1 ]; then
@@ -139,11 +307,6 @@ else
 	pstatus red "VULNERABLE" "PTI is needed to mitigate the vulnerability"
 fi
 
+/bin/echo
 
-echo
+[ -n "$vmlinux" -a -f "$vmlinux" ] && rm -f "$vmlinux"
-if [ "$USER" != root ]; then
-	echo "Note that you should launch this script with root privileges to get accurate information"
-	echo "You can try the following command: sudo $0"
-fi
-
-