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

[slackware-security]  Slackware 15.0 kernel (SSA:2022-067-01)

New kernel packages are available for Slackware 15.0 to fix security issues.


Here are the details from the Slackware 15.0 ChangeLog:
+--------------------------+
patches/packages/linux-5.15.27/*:  Upgraded.
  These updates fix various bugs and security issues, including the recently
  announced "Dirty Pipe" vulnerability which allows overwriting data in
  arbitrary read-only files (CVE-2022-0847).
  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.20:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0492
    Fixed in 5.15.23:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0516
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0435
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0487
    Fixed in 5.15.24:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25375
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25258
    Fixed in 5.15.25:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0847
    Fixed in 5.15.26:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25636
  (* Security fix *)
+--------------------------+


Where to find the new packages:
+-----------------------------+

Thanks to the friendly folks at the OSU Open Source Lab
(http://osuosl.org) for donating FTP and rsync hosting
to the Slackware project!  :-)

Also see the "Get Slack" section on http://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:
2a85a2797772459ca80df03a5ed769e3  kernel-generic-5.15.27-i586-1.txz
15119e1d6ef2490954ff635b6ccb5fe2  kernel-generic-smp-5.15.27_smp-i686-1.txz
ed85b4ee5670ec878a941102835c13e8  kernel-headers-5.15.27_smp-x86-1.txz
ccd62618252d7f4c030eae7fd3d5129b  kernel-huge-5.15.27-i586-1.txz
61ca0e30fc9e28fbfa2b858630962fb0  kernel-huge-smp-5.15.27_smp-i686-1.txz
0e391f69e52e76d47a7908be87f0aee8  kernel-modules-5.15.27-i586-1.txz
43770e99461b9f2ce89660a732e8e74e  kernel-modules-smp-5.15.27_smp-i686-1.txz
807820a51fce06d90ba50e28ad3d9a56  kernel-source-5.15.27_smp-noarch-1.txz

Slackware x86_64 15.0 packages:
926aab0cb4bd96fbe5553cf13d6afac8  kernel-generic-5.15.27-x86_64-1.txz
04d89ece2998fd8da2c4639c3733e2d6  kernel-headers-5.15.27-x86-1.txz
b1c4db383ecc04f48d8f250cbc6aae0a  kernel-huge-5.15.27-x86_64-1.txz
a727615770b69fd01923f27b97900b1b  kernel-modules-5.15.27-x86_64-1.txz
15c383b260409e747a6b765eb1efc9b2  kernel-source-5.15.27-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 15.0):
# /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 5.15.27-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.27 | 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.27-smp version when running
mkinitrd_command_generator. Note that this is only for 32-bit -- 64-bit
systems should always use 5.15.27 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.


+-----+