Alerts This Week
Warning Icon 1 566
Alerts This Week
Warning Icon 1 566

Slackware 14.2 SSA:2021-202-01 Moderate: Kernel Local Elevation Issue

slackware
Calendar Grey July 21, 2021
Dist Slackware Esm H88
Updated Slackware 14.2 kernel modules patching a local privilege escalation vulnerability. Critical security enhancements were implemented.
New kernel packages are available for Slackware 14.2 to fix a security issue

Summary

Here are the details from the Slackware 14.2 ChangeLog: Wed Jul 21 05:30:44 UTC 2021 patches/packages/linux-4.4.276/*: Upgraded. These updates fix various bugs and security issues, including the recently announced local privilege escalation vulnerability in the filesystem layer (CVE-2021-33909). 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://https://www.qualys.com/2021/07/20/cve-2021-33909/sequoia-local-privilege-escalation-linux.txt Fixed in 4.4.262: https://www.cve.org/CVERecord?id=CVE-2019-19060 https://www.cve.org/CVERecord?id=CVE-2019-19061 https://www.cve.org/CVERecord?id=CVE-2021-28660

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: 7448b2c6b59a644676d96ab85712e61e kernel-generic-4.4.276-i586-1.txz 3bd670f094978f92f952e1413259f02e kernel-generic-smp-4.4.276_smp-i686-1.txz f7641f1c4fd3f985e65678fef6b289de kernel-headers-4.4.276_smp-x86-1.txz 4c9e16c5c2fd3519f83dbbe73701901f kernel-huge-4.4.276-i586-1.txz 89e381bdb866be421437d1736158c523 kernel-huge-smp-4.4.276_smp-i686-1.txz e724f693e995d3e09a29528afbbfb3d8 kernel-modules-4.4.276-i586-1.txz 2eb13babd21e5fcfb67e4a7340d585eb kernel-modules-smp-4.4.276_smp-i686-1.txz 4e5eedd4f157d239ce69661ee480c3cd kernel-source-4.4.276_smp-noarch-1.txz
Slackware x86_64 14.2 packages: 4fe4c95f02a3cbf102a1e55fb3fada4b kernel-generic-4.4.276-x86_64-1.txz 93d82f7afaa97d3883f823aed2cb1ab5 kernel-headers-4.4.276-x86-1.txz daa4891c599c1f70caabeb034ee1714f kernel-huge-4.4.276-x86_64-1.txz 652ca6026a9db83a4a4b54416974101c kernel-modules-4.4.276-x86_64-1.txz e3a3ef38df2b45bffddac8be360e7ff3 kernel-source-4.4.276-noarch-1.txz

Severity
important
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.276-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.276 | 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.276-smp version when running mkinitrd_command_generator. Note that this is only for 32-bit -- 64-bit systems should always use 4.4.276 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