Alerts This Week
Warning Icon 1 697
Alerts This Week
Warning Icon 1 697

Slackware 15.0: 2023-048-01 Critical: Kernel Security Issues

slackware
Calendar Grey February 18, 2023
Dist Slackware Esm H88
Recent updates to kernel components for Slackware 15.0 have been released to address urgent security vulnerabilities and technical issues reliably.
New kernel packages are available for Slackware 15.0 to fix security issues

Summary

Here are the details from the Slackware 15.0 ChangeLog: patches/packages/linux-5.15.80/*: Upgraded. These updates fix various bugs and security issues. 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 5.15.81: https://www.cve.org/CVERecord?id=CVE-2022-47519 https://www.cve.org/CVERecord?id=CVE-2022-47518 https://www.cve.org/CVERecord?id=CVE-2022-47520 https://www.cve.org/CVERecord?id=CVE-2022-47521 https://www.cve.org/CVERecord?id=CVE-2022-3344 Fixed in 5.15.82: https://www.cve.org/CVERecord?id=CVE-2022-45869 https://www.cve.org/CVERecord?id=CVE-2022-4378 Fixed in 5.15.83:

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 15.0:
Updated packages for Slackware x86_64 15.0:

MD5 Signatures

Slackware 15.0 packages: 09a2dee7bc0acd2c51f9bda0e527d939 kernel-generic-5.15.94-i586-1.txz 7cfba1a12d9873e19773862ec08a326a kernel-generic-smp-5.15.94_smp-i686-1.txz 7d92781ac28b26e639a01715868bf743 kernel-headers-5.15.94_smp-x86-1.txz c2fa0456a7d6356503a522f5bce07b99 kernel-huge-5.15.94-i586-1.txz 12454c00fe068f733cfd0b98151d7c6f kernel-huge-smp-5.15.94_smp-i686-1.txz c7f88278a84e3b51560911ad1d105370 kernel-modules-5.15.94-i586-1.txz c9d4085ce1cbf14869b820d8267d6f7f kernel-modules-smp-5.15.94_smp-i686-1.txz 209e8286990650a43a96538420ca37f2 kernel-source-5.15.94_smp-noarch-1.txz
Slackware x86_64 15.0 packages: 48e682a693e5ae282395073be4fc7a75 kernel-generic-5.15.94-x86_64-1.txz acbc2d8a628bb554175cb33eb30e7b42 kernel-headers-5.15.94-x86-1.txz b214ee6ed65c9846b2fdac4dea37bea5 kernel-huge-5.15.94-x86_64-1.txz be5a272d628ebd198d05eb75c4d15321 kernel-modules-5.15.94-x86_64-1.txz 5322d656de22e3015ca6ea20ac7d3003 kernel-source-5.15.94-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 15.0): # /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 5.15.94-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 15.0): # /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 5.15.94 | 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 5.15.94-smp version when running mkinitrd_command_generator. Note that this is only for 32-bit -- 64-bit systems should always use 5.15.94 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