-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[slackware-security] Slackware 14.2 kernel (SSA:2018-264-01)

New kernel packages are available for Slackware 14.2 to fix a security issue.


Here are the details from the Slackware 14.2 ChangeLog:
+--------------------------+
patches/packages/linux-4.4.157/*:  Upgraded.
  This kernel removes the unnecessary vmacache_flush_all code which could have
  led to a use-after-free situation and potentially local privilege escalation.
  In addition, it fixes some regressions which may have led to diminished X
  performance.
  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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17182
  (* Security fix *)
+--------------------------+


Where to find the 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:
4cbc3917d30e3ec997f23aadfbb20d2f  kernel-firmware-20180913_44d4fca-noarch-1.txz
df3e3e6e806a744b5c2a85ca9a581666  kernel-generic-4.4.157-i586-1.txz
4786d7445be8ff55f83be49ac7762703  kernel-generic-smp-4.4.157_smp-i686-1.txz
c1a300d12e24e2321e0b9b30cddbdf5f  kernel-headers-4.4.157_smp-x86-1.txz
b19ce77fa8dd71de87f79237619610bf  kernel-huge-4.4.157-i586-1.txz
0e3bfc4ca162f7e804f9503355d85bec  kernel-huge-smp-4.4.157_smp-i686-1.txz
8bf4a2236dae7c3c4bdbac5df2e4818e  kernel-modules-4.4.157-i586-1.txz
edaaa0d85fba3e7181f94ab8c3f21dfb  kernel-modules-smp-4.4.157_smp-i686-1.txz
0f67c5ebc78917d5e94bf07bcdefb8b6  kernel-source-4.4.157_smp-noarch-1.txz

Slackware x86_64 14.2 packages:
4cbc3917d30e3ec997f23aadfbb20d2f  kernel-firmware-20180913_44d4fca-noarch-1.txz
4e50bbe9a3b7232aeb0679eda5325f87  kernel-generic-4.4.157-x86_64-1.txz
ef8d303cfa4855d39a28f94181752936  kernel-headers-4.4.157-x86-1.txz
9f531d40bd2151bc0276f8cb5342c38c  kernel-huge-4.4.157-x86_64-1.txz
9911b7530358ba7877eacc8bf1c7d215  kernel-modules-4.4.157-x86_64-1.txz
91cfbd23a457cdf43ddcfd6b4ae567a5  kernel-source-4.4.157-noarch-1.txz


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


+-----+