Slackware 14.2 Kernel Update: SSA:2022-031-01 Critical Security Fix
Summary
Here are the details from the Slackware 14.2 ChangeLog: patches/packages/linux-4.4.301/*: Upgraded. These updates fix various bugs and security issues, including the recently announced i915 issue that could lead to user-space gaining access to random memory pages (CVE-2022-0330). 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: https://seclists.org/oss-sec/2022/q1/81 Fixed in 4.4.277: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-38204 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3679 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-37576 Fixed in 4.4.278: https://cve.mitre.org/cgi-bin/cvename.cgi?nam...
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:
ftp://ftp.slackware.com/pub/slackware/slackware-14.2/patches/packages/linux-4.4.301/kernel-generic-4.4.301-i586-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware-14.2/patches/packages/linux-4.4.301/kernel-generic-smp-4.4.301_smp-i686-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware-14.2/patches/packages/linux-4.4.301/kernel-headers-4.4.301_smp-x86-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware-14.2/patches/packages/linux-4.4.301/kernel-huge-4.4.301-i586-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware-14.2/patches/packages/linux-4.4.301/kernel-huge-smp-4.4.301_smp-i686-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware-14.2/patches/packages/linux-4.4.301/kernel-modules-4.4.301-i586-1...
MD5 Signatures
Slackware 14.2 packages:
5a3d424a58c0f5551029317714d9b792 kernel-generic-4.4.301-i586-1.txz
4627a5b1f571b6c851368a7d1b48b8f3 kernel-generic-smp-4.4.301_smp-i686-1.txz
2002a1e767d6300e3f05b8706bd672db kernel-headers-4.4.301_smp-x86-1.txz
6fd01f921b15ad2b67c4709cfaeb2c58 kernel-huge-4.4.301-i586-1.txz
0de729d8ecd6ead7fd18f51f4c081023 kernel-huge-smp-4.4.301_smp-i686-1.txz
1694fc4e440ae22acfbdba30f5bbf64b kernel-modules-4.4.301-i586-1.txz
2ac1a18d9addc56b1ec5fe3c0bee1810 kernel-modules-smp-4.4.301_smp-i686-1.txz
cddf16c1eb85dbf0511f4c2e914e161c kernel-source-4.4.301_smp-noarch-1.txz
Slackware x86_64 14.2 packages:
b83b2079191cab1415b9e76e90ef8bc5 kernel-generic-4.4.301-x86_64-1.txz
8dd8e62fed72120908c3c72734d35eb6 kernel-headers-4.4.301-x86-1.txz
b491805626590da0be9e3985cf0577fe kernel-huge-4.4.301-x86_64-1.txz
a57ae4b84879f831f68241a94b797816 kernel-modules-4.4.301-x86_64-1.txz
641738fc28a1ddb9093934735719ec60 kernel-source-4.4.301-noarch-1.txz
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.301-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.301 | 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.301-smp version when running mkinitrd_command_generator. Note that this is only for 32-bit -- 64-bit systems should always use 4.4.301 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.
