Alerts This Week
Warning Icon 1 560
Alerts This Week
Warning Icon 1 560

Slackware 14.2: SSA:2020-163-01 Critical: Kernel Security Update

slackware
Calendar Grey June 11, 2020
Dist Slackware Esm H88
Important kernel updates address severe vulnerabilities in Slackware 14.2. Ensure your kernel packages are updated to enhance security.
New kernel packages are available for Slackware 14.2 to fix security issues

Summary

Here are the details from the Slackware 14.2 ChangeLog: patches/packages/linux-4.4.227/*: Upgraded. These updates fix various bugs and security issues, including a mitigation for SRBDS (Special Register Buffer Data Sampling). SRBDS is an MDS-like speculative side channel that can leak bits from the random number generator (RNG) across cores and threads. Be sure to upgrade your initrd after upgrading the kernel packages. If you use lilo to boot your machine, be sure lilo.conf points to the correct kernel and initrd and run lilo as root to update the bootloader. If you use elilo to boot your machine, you should run eliloconfig to copy the kernel and initrd to the EFI System Partition. For more information, see: Fixed in 4.4.218: https://www.cve.org/CVERecord?id=CVE-2020-11668 https://www.cve.org/CVERecord?id=CVE-2020-11608 https://www.cve.org/CVERecord?id=CVE-2020-11609 https://www.cve.org/CVERecord?id=CVE-2020-10942 Fixed in 4.4.219:

Read the Full Advisory

Where Find New Packages

Thanks to the friendly folks at the OSU Open Source Lab (https://osuosl.org/) for donating FTP and rsync hosting to the Slackware project! :-)
Also see the "Get Slack" section on http://www.slackware.com/ for additional mirror sites near you.
Updated packages for Slackware 14.2:
Updated packages for Slackware x86_64 14.2:

MD5 Signatures

Slackware 14.2 packages: 9a40d88eccfd6fd52ff545cefe86f87b kernel-generic-4.4.227-i586-1.txz c13f5fa4ef1e1b205b55b8200a82164d kernel-generic-smp-4.4.227_smp-i686-1.txz 98070c7ae594d9cd3c5a7d2a81aefb79 kernel-headers-4.4.227_smp-x86-1.txz 1411df7a758aa56ab7352ab251c33187 kernel-huge-4.4.227-i586-1.txz edae1a14db491ed3704e97cb5f78e846 kernel-huge-smp-4.4.227_smp-i686-1.txz 4f0b746f0eda80865a5507485f220c8c kernel-modules-4.4.227-i586-1.txz bc4c4a2c3cfb5c51457965dc95d44331 kernel-modules-smp-4.4.227_smp-i686-1.txz 3dfd157f38293392f5ca8ce935e70b8c kernel-source-4.4.227_smp-noarch-1.txz
Slackware x86_64 14.2 packages: 6c8ff864c67d0f5d47b1ed13a81fc912 kernel-generic-4.4.227-x86_64-1.txz 2a768057dd773822621dfcf069e6edea kernel-headers-4.4.227-x86-1.txz 25480853bc1c014faed7285517aaa1b1 kernel-huge-4.4.227-x86_64-1.txz 832fe6fa4b00c166f9467208c1e47d9d kernel-modules-4.4.227-x86_64-1.txz 3b83ef123fbc7fe8b5d7957f1a08c3e4 kernel-source-4.4.227-noarch-1.txz

Severity
critical
Lowest
Low
Medium
High
Critical

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Installation Instructions

Installation instructions: Upgrade the packages as root: # upgradepkg kernel-*.txz If you are using an initrd, you'll need to rebuild it. For a 32-bit SMP machine, use this command (substitute the appropriate kernel version if you are not running Slackware 14.2): # /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 4.4.227-smp | bash For a 64-bit machine, or a 32-bit uniprocessor machine, use this command (substitute the appropriate kernel version if you are not running Slackware 14.2): # /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 4.4.227 | bash Please note that "uniprocessor" has to do with the kernel you are running, not with the CPU. Most systems should run the SMP kernel (if they can) regardless of the number of cores the CPU has. If you aren't sure which kernel you are running, run "uname -a". If you see SMP there, you are running the SMP kernel and should use the 4.4.227-smp version when running mkinitrd_command_generator. Note that this is only for 32-bit -- 64-bit systems should always use 4.4.227 as the version. If you are using lilo or elilo to boot the machine, you'll need to ensure that the machine is properly prepared before rebooting. If using LILO: By default, lilo.conf contains an image= line that references a symlink that always points to the correct kernel. No editing should be required unless your machine uses a custom lilo.conf. If that is the case, be sure that the image= line references the correct kernel file. Either way, you'll need to run "lilo" as root to reinstall the boot loader. If using elilo: Ensure that the /boot/vmlinuz symlink is pointing to the kernel you wish to use, and then run eliloconfig to update the EFI System Partition.

Related News

Your message here