A kernel security update has been released for Slackware Linux 15.0.

slackware-security: Slackware 15.0 kernel (SSA:2022-237-02)

[slackware-security] Slackware 15.0 kernel (SSA:2022-237-02)

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.63/*: 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.39:
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1974
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1975
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1734
Fixed in 5.15.40:
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1943
Fixed in 5.15.41:
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28893
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32296
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1012
Fixed in 5.15.42:
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1652
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1729
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21499
Fixed in 5.15.44:
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1789
Fixed in 5.15.45:
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2873
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1966
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32250
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2078
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1852
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1972
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2503
Fixed in 5.15.46:
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1184
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1973
Fixed in 5.15.47:
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34494
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34495
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32981
Fixed in 5.15.48:
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21125
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21166
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21123
Fixed in 5.15.53:
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2318
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-33743
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-33742
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-33741
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-33740
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-26365
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-33744
Fixed in 5.15.54:
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33655
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34918
Fixed in 5.15.56:
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-36123
Fixed in 5.15.57:
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29900
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29901
Fixed in 5.15.58:
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21505
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1462
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-36879
Fixed in 5.15.59:
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-36946
Fixed in 5.15.60:
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-26373
Fixed in 5.15.61:
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2586
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2585
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1679
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2588
(* 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! :-)

Updated packages for Slackware 15.0:
  ftp://ftp.slackware.com/pub/slackware/slackware-15.0/patches/packages/linux-5.15.63/kernel-generic-5.15.63-i586-1.txz
  ftp://ftp.slackware.com/pub/slackware/slackware-15.0/patches/packages/linux-5.15.63/kernel-generic-smp-5.15.63_smp-i686-1.txz
  ftp://ftp.slackware.com/pub/slackware/slackware-15.0/patches/packages/linux-5.15.63/kernel-headers-5.15.63_smp-x86-1.txz
  ftp://ftp.slackware.com/pub/slackware/slackware-15.0/patches/packages/linux-5.15.63/kernel-huge-5.15.63-i586-1.txz
  ftp://ftp.slackware.com/pub/slackware/slackware-15.0/patches/packages/linux-5.15.63/kernel-huge-smp-5.15.63_smp-i686-1.txz
  ftp://ftp.slackware.com/pub/slackware/slackware-15.0/patches/packages/linux-5.15.63/kernel-modules-5.15.63-i586-1.txz
  ftp://ftp.slackware.com/pub/slackware/slackware-15.0/patches/packages/linux-5.15.63/kernel-modules-smp-5.15.63_smp-i686-1.txz
  ftp://ftp.slackware.com/pub/slackware/slackware-15.0/patches/packages/linux-5.15.63/kernel-source-5.15.63_smp-noarch-1.txz

Updated packages for Slackware x86_64 15.0:
  ftp://ftp.slackware.com/pub/slackware/slackware64-15.0/patches/packages/linux-5.15.63/kernel-generic-5.15.63-x86_64-1.txz
  ftp://ftp.slackware.com/pub/slackware/slackware64-15.0/patches/packages/linux-5.15.63/kernel-headers-5.15.63-x86-1.txz
  ftp://ftp.slackware.com/pub/slackware/slackware64-15.0/patches/packages/linux-5.15.63/kernel-huge-5.15.63-x86_64-1.txz
  ftp://ftp.slackware.com/pub/slackware/slackware64-15.0/patches/packages/linux-5.15.63/kernel-modules-5.15.63-x86_64-1.txz
  ftp://ftp.slackware.com/pub/slackware/slackware64-15.0/patches/packages/linux-5.15.63/kernel-source-5.15.63-noarch-1.txz

MD5 signatures:
+-------------+

Slackware 15.0 packages:
5c31aac999b00d15a783e6094f637532 kernel-generic-5.15.63-i586-1.txz
6f8347f7b51fb9b27874d77b94ec6f30 kernel-generic-smp-5.15.63_smp-i686-1.txz
311adc6da684773615a101ea19414113 kernel-headers-5.15.63_smp-x86-1.txz
9beb03283db3704d81b2d5891a02aa53 kernel-huge-5.15.63-i586-1.txz
4ef4877067f5e7c48e72d1454f0356bc kernel-huge-smp-5.15.63_smp-i686-1.txz
a8bc611fb93241a04e3ab3a8341fa16d kernel-modules-5.15.63-i586-1.txz
b5d3943050cc989ca2ff38cd8e9f8d57 kernel-modules-smp-5.15.63_smp-i686-1.txz
d4af5bb1a638d16f2f12c59330b6a4ed kernel-source-5.15.63_smp-noarch-1.txz

Slackware x86_64 15.0 packages:
3d90053137ecf7d6bba568f5220abfa3 kernel-generic-5.15.63-x86_64-1.txz
9e9140aee3e53f89c91e0da799b23938 kernel-headers-5.15.63-x86-1.txz
16a28b95d3918edc031ae3052851a003 kernel-huge-5.15.63-x86_64-1.txz
d60d98fd8308a12addffc3cec220729f kernel-modules-5.15.63-x86_64-1.txz
b7c3de6e71d39a80c7132c30799310ec kernel-source-5.15.63-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.63-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.63 | 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.63-smp version when running
mkinitrd_command_generator. Note that this is only for 32-bit -- 64-bit
systems should always use 5.15.63 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.