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

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

New kernel packages are available for Slackware 14.2 to fix a regression in the
getsockopt() function and to fix two denial-of-service security issues.


Here are the details from the Slackware 14.2 ChangeLog:
+--------------------------+
patches/packages/linux-4.4.132/*:  Upgraded.
  This kernel upgrade is being provided primarily to fix a regression in the
  getsockopt() function, but it also contains fixes for two denial-of-service
  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:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000004
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1092
  (* 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:
4ff85b42f4f7587deefcb84ce14c9461  kernel-firmware-20180518_2a9b2cf-noarch-1.txz
566064dfcb36625c610a6b0e55855a41  kernel-generic-4.4.132-i586-1.txz
b92dc964c1756631c46005070047ac60  kernel-generic-smp-4.4.132_smp-i686-1.txz
5895d6a019ff0ce3da4bdb661b722b6b  kernel-headers-4.4.132_smp-x86-1.txz
36a7a69c61c50d76de322c9b3fd23bcd  kernel-huge-4.4.132-i586-1.txz
f53fef4887719b6688b639c96fc5e2af  kernel-huge-smp-4.4.132_smp-i686-1.txz
750d2a9bef5c7541927c9771a5bca8fd  kernel-modules-4.4.132-i586-1.txz
47717aecee869d4328799ede9a58a8b8  kernel-modules-smp-4.4.132_smp-i686-1.txz
61b6014daedfc3959ec3c05811619545  kernel-source-4.4.132_smp-noarch-1.txz

Slackware x86_64 14.2 packages:
4ff85b42f4f7587deefcb84ce14c9461  kernel-firmware-20180518_2a9b2cf-noarch-1.txz
0dfe6a39b86d1a261b4be59c8fe4be6a  kernel-generic-4.4.132-x86_64-1.txz
f0154ba85c2414df180ca5807f489518  kernel-headers-4.4.132-x86-1.txz
c602c39608615e542f7a729f47296c23  kernel-huge-4.4.132-x86_64-1.txz
073d1cef1df2762916478f7008be7adc  kernel-modules-4.4.132-x86_64-1.txz
e32b5fd02a085b1ece9fb7d98c55f396  kernel-source-4.4.132-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.132-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.132 | 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.132-smp version when running
mkinitrd_command_generator.  Note that this is only for 32-bit -- 64-bit
systems should always use 4.4.132 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.


+-----+