The Latest Kernel Release.

enorbet · 01-31-2018, 11:13 PM

Today I tried to install the nVidia 390.25 full release on my 14.2 Multilib with a custom 4.14.12 kernel that had the beta version installed and working great for a few weeks now. The full release driver would not build even though the beta 390.12 Beta built with no issues at all. I searched for "nVidia 390.25 kernel 4.14.12" and got a hit for a page saying 4.15 kernel final was out and that nVidia new drivers built just fine on it. So I downloaded the tarball, did make oldconfig, and built and installed it, booted first time and installed nVidia Full Release without nary a peep. Works great. I'm pleased.

cwizardone · 02-02-2018, 04:15 AM

I didn't try to build the 390.25 driver with the 4.14.12 kernel, but it did build with the 4.14.15 kernel. As you have experienced, the 390.25 Long Term driver has also worked extremely well with the 4.15 kernel.

cwizardone · 02-03-2018, 02:20 PM

Kernel updates 4.15.1, 4.14.17, 4.9.80, and 4.4.115 are now available at, https://www.kernel.org/.

The change logs,

https://cdn.kernel.org/pub/linux/ker...angeLog-4.15.1

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.14.17

https://cdn.kernel.org/pub/linux/ker...angeLog-4.9.80

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.4.115

Lysander666 · 02-07-2018, 02:56 PM

Hmm installed the new kernel and the checker tool says I'm not protected against Meltdown, odd.

Code:

Spectre and Meltdown mitigation detection tool v0.29

Checking for vulnerabilities against running kernel Linux 4.4.115-smp #2 SMP Mon Feb 5 22:30:37 CST 2018 i686
CPU is Intel(R) Atom(TM) CPU N270 @ 1.60GHz

CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1'
* Checking whether we're safe according to the /sys interface:  NO  (kernel confirms your system is vulnerable)
STATUS:  VULNERABLE  (Vulnerable)

CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
* Checking whether we're safe according to the /sys interface:  YES  (kernel confirms that the mitigation is active)
STATUS:  NOT VULNERABLE  (Mitigation: Full generic retpoline)

CVE-2017-5754 [rogue data cache load] aka 'Meltdown' aka 'Variant 3'
* Checking whether we're safe according to the /sys interface:  NO  (kernel confirms your system is vulnerable)
STATUS:  VULNERABLE  (Vulnerable)

A false sense of security is worse than no security at all, see --disclaimer
bash-4.3# exit

EDIT: I was using an out of date tool. Newer version from here https://github.com/speed47/spectre-meltdown-checker

Code:

bash-4.3# ./spectre-meltdown-checker.sh
Spectre and Meltdown mitigation detection tool v0.34+

Checking for vulnerabilities on current system
Kernel is Linux 4.4.115-smp #2 SMP Mon Feb 5 22:30:37 CST 2018 i686
CPU is Intel(R) Atom(TM) CPU N270   @ 1.60GHz

Hardware check
* Hardware support (CPU microcode) for mitigation techniques
  * Indirect Branch Restricted Speculation (IBRS)
    * SPEC_CTRL MSR is available:  NO
    * CPU indicates IBRS capability:  NO
  * Indirect Branch Prediction Barrier (IBPB)
    * PRED_CMD MSR is available:  NO
    * CPU indicates IBPB capability:  NO
  * Single Thread Indirect Branch Predictors (STIBP)
    * SPEC_CTRL MSR is available:  NO
    * CPU indicates STIBP capability:  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 (RDCL_NO):  NO
  * CPU microcode is known to cause stability problems:  NO  (model 28 stepping 2 ucode 0x20a)
* CPU vulnerability to the three speculative execution attacks variants
  * Vulnerable to Variant 1:  NO
  * Vulnerable to Variant 2:  NO
  * Vulnerable to Variant 3:  NO

CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1'
* Mitigated according to the /sys interface:  NO  (kernel confirms your system is vulnerable)
* Kernel has array_index_mask_nospec:  NO
* Checking count of LFENCE instructions following a jump in kernel...  NO  (only 0 jump-then-lfence instructions found, should be >= 30 (heuristic))
STATUS:  NOT VULNERABLE  (your CPU vendor reported your CPU model as not vulnerable)

CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
* Mitigated according to the /sys interface:  YES  (kernel confirms that the mitigation is active)
* Mitigation 1
  * Kernel is compiled with IBRS/IBPB support:  NO
  * Currently enabled features
    * IBRS enabled for Kernel space:  NO
    * IBRS enabled for User space:  NO
    * IBPB enabled:  NO
* Mitigation 2
  * Kernel compiled with retpoline option:  YES
  * Kernel compiled with a retpoline-aware compiler:  YES  (kernel reports full retpoline compilation)
  * Retpoline enabled:  YES
STATUS:  NOT VULNERABLE  (your CPU vendor reported your CPU model as not vulnerable)

CVE-2017-5754 [rogue data cache load] aka 'Meltdown' aka 'Variant 3'
* Mitigated according to the /sys interface:  NO  (kernel confirms your system is vulnerable)
* Kernel supports Page Table Isolation (PTI):  NO
* PTI enabled and active:  NO
* Running as a Xen PV DomU:  NO
STATUS:  NOT VULNERABLE  (your CPU vendor reported your CPU model as not vulnerable)

A false sense of security is worse than no security at all, see --disclaimer

Forgot - I'm in that very small percentage who aren't affected anyway.

kjhambrick · 02-07-2018, 03:11 PM

EDIT: I am too slow ... I'll have to update my version of spectre-meltdown-checker.sh

Lysander666 ---

Maybe the Atom N270 is one of the ~10-Year Old Processors that will receive the Meltdown PTI Firmware fix 'later' ?

-- kjh

This gawk command will print the CPU Vulnerabilities and whether or not it is mitigated according to the Kernel.

For my i7 6700K laptop with a self-built 4.4.115 Kernel:

Code:

# gawk '{ print FILENAME ":\t" $0 }' /sys/devices/system/cpu/vulnerabilities/*

/sys/devices/system/cpu/vulnerabilities/meltdown:       Mitigation: PTI
/sys/devices/system/cpu/vulnerabilities/spectre_v1:     Vulnerable
/sys/devices/system/cpu/vulnerabilities/spectre_v2:     Vulnerable: Minimal generic ASM retpoline

Lysander666 · 02-07-2018, 03:23 PM

Ah thanks for that. I get

Code:

bash-4.3# gawk '{ print FILENAME ":\t" $0 }' /sys/devices/system/cpu/vulnerabilities/*

/sys/devices/system/cpu/vulnerabilities/meltdown:	Vulnerable
/sys/devices/system/cpu/vulnerabilities/spectre_v1:	Vulnerable
/sys/devices/system/cpu/vulnerabilities/spectre_v2:	Mitigation: Full generic retpoline

So the 0.29 was still correct. Interesting. I wonder that it's because of the CPU that there's no Meltdown mitigation there.

Not that I can apparently be affected but it's still nice to know.

kjhambrick · 02-07-2018, 04:09 PM

All --

Kernels 4.15.2, 4.14.18 and 3.18.94 are now available.

Handy Links:

Code:

stable:    4.15.2        Source ChangeLog 2018-02-07
stable:    4.14.18       Source ChangeLog 2018-02-07 ( Slackware-current )
longterm:  3.18.94 [EOL] Source ChangeLog 2018-02-07

No CVE References were found for 4.15.2, 4.14.18 or 3.18.94

As always, do check the ChangeLogs for other security-related fixes.

Check for the Latest Updates at www.kernel.org.

Have Fun All'Y'All !

-- kjh

kjhambrick · 02-07-2018, 04:21 PM

Quote:

Originally Posted by Lysander666

Ah thanks for that. I get

Code:

bash-4.3# gawk '{ print FILENAME ":\t" $0 }' /sys/devices/system/cpu/vulnerabilities/*

/sys/devices/system/cpu/vulnerabilities/meltdown:	Vulnerable
/sys/devices/system/cpu/vulnerabilities/spectre_v1:	Vulnerable
/sys/devices/system/cpu/vulnerabilities/spectre_v2:	Mitigation: Full generic retpoline

So the 0.29 was still correct. Interesting. I wonder that it's because of the CPU that there's no Meltdown mitigation there.

Not that I can apparently be affected but it's still nice to know.

Lysander666 --

Hoo boy ... I don't know the status of all this from minute-to-minute and from system-to-system ... I am so confused

I do have a LWN subscription and Jonathan Corbet published Meltdown and Spectre mitigations — a February update ( subscribers only ) on Monday, Feb 5 which means the Article will be openly available next Monday, Feb 12 or so.

To the best of my understanding, on Intel Processors, Meltdown MAY be mitigated via the PTI Firmware Patch, there is no mitigation yet for Spectre v1 and the recent retpoline updates to gcc, glibc and the Kernel can fix Spctre v2 ... but remember, I confused

-- kjh

Coastal Disturbance · 02-08-2018, 12:00 PM

Nice!

Code:

% uname -rms
Linux 4.14.18 x86_64

% awk '{ print FILENAME ":\t" $0 }' /sys/devices/system/cpu/vulnerabilities/* 
/sys/devices/system/cpu/vulnerabilities/meltdown:	Mitigation: PTI
/sys/devices/system/cpu/vulnerabilities/spectre_v1:	Mitigation: __user pointer sanitization
/sys/devices/system/cpu/vulnerabilities/spectre_v2:	Mitigation: Full generic retpoline

yvesjv · 02-08-2018, 03:37 PM

Just installed 4.15.2 and looks like Meltdown and Spectre1/2 are fixed.

Lysander666 · 02-08-2018, 04:07 PM

Great news. Hope the full fixes come over to Slackware stable [and Debian] very soon.

55020 · 02-08-2018, 04:36 PM

If you're using kernel 4.15 on Slackware 14.2, the crda package from -current (crda-3.18-x86_64-5) can be installed on 14.2 and works great, if you need the regulatory.db file (thanks RandomTroll).

In other 4.15 news, b43 wifi isn't working. They didn't mention queueing that patch for stable....

Paulo2 · 02-08-2018, 05:33 PM

It seems that only with 4.14.18 (maybe next kernel for -current

) and 4.15.2 the Spectre v1 is mitigated.

Code:

root@paulobash~# cat 4.14.17-x86_64 
/sys/devices/system/cpu/vulnerabilities/meltdown:       Not affected
/sys/devices/system/cpu/vulnerabilities/spectre_v1:     Vulnerable
/sys/devices/system/cpu/vulnerabilities/spectre_v2:     Mitigation: Full AMD retpoline

root@paulobash~# cat 4.15.1-custom-x86_64 
/sys/devices/system/cpu/vulnerabilities/meltdown:       Not affected
/sys/devices/system/cpu/vulnerabilities/spectre_v1:     Vulnerable
/sys/devices/system/cpu/vulnerabilities/spectre_v2:     Mitigation: Full AMD retpoline

Lysander666 · 02-09-2018, 06:36 AM

Quote:

Originally Posted by Paulo2

It seems that only with 4.14.18 (maybe next kernel for -current

) and 4.15.2 the Spectre v1 is mitigated.

Code:

root@paulobash~# cat 4.14.17-x86_64 
/sys/devices/system/cpu/vulnerabilities/meltdown:       Not affected
/sys/devices/system/cpu/vulnerabilities/spectre_v1:     Vulnerable
/sys/devices/system/cpu/vulnerabilities/spectre_v2:     Mitigation: Full AMD retpoline

root@paulobash~# cat 4.15.1-custom-x86_64 
/sys/devices/system/cpu/vulnerabilities/meltdown:       Not affected
/sys/devices/system/cpu/vulnerabilities/spectre_v1:     Vulnerable
/sys/devices/system/cpu/vulnerabilities/spectre_v2:     Mitigation: Full AMD retpoline

In 64bit. 32bit users are being rather left behind here. No mitigation for Meltdown as yet.

kjhambrick · 02-09-2018, 06:37 AM

Today's Slackware64 current 4.14.18 update fixes Spectre v1 on my test box:

Code:

# uname -a

Linux samsung.kjh.home 4.14.18 #1 SMP Thu Feb 8 12:48:42 CST 2018 x86_64 Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz GenuineIntel GNU/Linux

4.4.17 ( updates thru Wed Feb 7 04:28:48 UTC 2018 )

Code:

/sys/devices/system/cpu/vulnerabilities/meltdown:       Mitigation: PTI
/sys/devices/system/cpu/vulnerabilities/spectre_v1:     Vulnerable
/sys/devices/system/cpu/vulnerabilities/spectre_v2:     Mitigation: Full generic retpoline

4.4.18 ( includes Fri Feb 9 02:50:56 UTC 2018 updates )

Code:

/sys/devices/system/cpu/vulnerabilities/meltdown:       Mitigation: PTI
/sys/devices/system/cpu/vulnerabilities/spectre_v1:     Mitigation: __user pointer sanitization
/sys/devices/system/cpu/vulnerabilities/spectre_v2:     Mitigation: Full generic retpoline

Thanks to Pat and the Team !

-- kjh( Woo Hoo (

! THUNK !

))