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

[slackware-security] Slackware 15.0 kernel (SSA:2023-325-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.139/*:  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.116:
    https://www.cve.org/CVERecord?id=CVE-2023-35788
    https://www.cve.org/CVERecord?id=CVE-2022-45887
    https://www.cve.org/CVERecord?id=CVE-2022-45886
    https://www.cve.org/CVERecord?id=CVE-2023-3212
    https://www.cve.org/CVERecord?id=CVE-2022-45919
    Fixed in 5.15.117:
    https://www.cve.org/CVERecord?id=CVE-2023-2124
    https://www.cve.org/CVERecord?id=CVE-2023-34255
    Fixed in 5.15.118:
    https://www.cve.org/CVERecord?id=CVE-2023-3609
    https://www.cve.org/CVERecord?id=CVE-2023-3117
    https://www.cve.org/CVERecord?id=CVE-2023-3390
    https://www.cve.org/CVERecord?id=CVE-2023-3338
    Fixed in 5.15.119:
    https://www.cve.org/CVERecord?id=CVE-2023-3610
    Fixed in 5.15.121:
    https://www.cve.org/CVERecord?id=CVE-2023-31248
    https://www.cve.org/CVERecord?id=CVE-2023-38432
    https://www.cve.org/CVERecord?id=CVE-2023-3866
    https://www.cve.org/CVERecord?id=CVE-2023-2898
    https://www.cve.org/CVERecord?id=CVE-2023-44466
    https://www.cve.org/CVERecord?id=CVE-2023-4132
    https://www.cve.org/CVERecord?id=CVE-2023-3611
    https://www.cve.org/CVERecord?id=CVE-2022-48502
    https://www.cve.org/CVERecord?id=CVE-2023-3865
    https://www.cve.org/CVERecord?id=CVE-2023-35001
    https://www.cve.org/CVERecord?id=CVE-2023-3776
    https://www.cve.org/CVERecord?id=CVE-2023-3863
    Fixed in 5.15.122:
    https://www.cve.org/CVERecord?id=CVE-2023-20593
    Fixed in 5.15.123:
    https://www.cve.org/CVERecord?id=CVE-2023-3777
    https://www.cve.org/CVERecord?id=CVE-2023-4004
    Fixed in 5.15.124:
    https://www.cve.org/CVERecord?id=CVE-2023-4015
    https://www.cve.org/CVERecord?id=CVE-2023-4147
    https://www.cve.org/CVERecord?id=CVE-2023-1206
    Fixed in 5.15.125:
    https://www.cve.org/CVERecord?id=CVE-2022-40982
    https://www.cve.org/CVERecord?id=CVE-2023-20569
    Fixed in 5.15.126:
    https://www.cve.org/CVERecord?id=CVE-2023-20588
    https://www.cve.org/CVERecord?id=CVE-2023-4128
    https://www.cve.org/CVERecord?id=CVE-2023-4208
    https://www.cve.org/CVERecord?id=CVE-2023-4206
    https://www.cve.org/CVERecord?id=CVE-2023-4207
    https://www.cve.org/CVERecord?id=CVE-2023-40283
    Fixed in 5.15.128:
    https://www.cve.org/CVERecord?id=CVE-2023-4569
    https://www.cve.org/CVERecord?id=CVE-2023-39194
    https://www.cve.org/CVERecord?id=CVE-2023-4273
    https://www.cve.org/CVERecord?id=CVE-2023-3772
    Fixed in 5.15.132:
    https://www.cve.org/CVERecord?id=CVE-2023-4921
    https://www.cve.org/CVERecord?id=CVE-2023-4623
    https://www.cve.org/CVERecord?id=CVE-2023-42753
    https://www.cve.org/CVERecord?id=CVE-2023-42752
    https://www.cve.org/CVERecord?id=CVE-2023-39189
    https://www.cve.org/CVERecord?id=CVE-2023-4881
    https://www.cve.org/CVERecord?id=CVE-2023-45871
    https://www.cve.org/CVERecord?id=CVE-2023-39193
    https://www.cve.org/CVERecord?id=CVE-2023-39192
    Fixed in 5.15.133:
    https://www.cve.org/CVERecord?id=CVE-2023-42755
    Fixed in 5.15.134:
    https://www.cve.org/CVERecord?id=CVE-2023-42754
    https://www.cve.org/CVERecord?id=CVE-2023-4563
    https://www.cve.org/CVERecord?id=CVE-2023-4244
    https://www.cve.org/CVERecord?id=CVE-2023-5197
    Fixed in 5.15.135:
    https://www.cve.org/CVERecord?id=CVE-2023-34324
    https://www.cve.org/CVERecord?id=CVE-2023-31085
    https://www.cve.org/CVERecord?id=CVE-2023-5158
    Fixed in 5.15.136:
    https://www.cve.org/CVERecord?id=CVE-2023-35827
    Fixed in 5.15.137:
    https://www.cve.org/CVERecord?id=CVE-2023-46813
    https://www.cve.org/CVERecord?id=CVE-2023-5717
    https://www.cve.org/CVERecord?id=CVE-2023-5178
  (* 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 15.0:

Updated packages for Slackware x86_64 15.0:


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

Slackware 15.0 packages:
8211588a7ce1578ea991bd5362f7445e  kernel-generic-5.15.139-i586-1.txz
64037b5079bfe0757445e074c7d3c7cb  kernel-generic-smp-5.15.139_smp-i686-1.txz
1a500cf7afe8e155302ac974aafa44d1  kernel-headers-5.15.139_smp-x86-1.txz
ace5996456652d42f14a94c1ba36b4f1  kernel-huge-5.15.139-i586-1.txz
6069f8f4da9f93504af0298735dee9aa  kernel-huge-smp-5.15.139_smp-i686-1.txz
984ad76bb952c3931e89210486466668  kernel-modules-5.15.139-i586-1.txz
d0dc77021b8169ed7365130bf221e454  kernel-modules-smp-5.15.139_smp-i686-1.txz
96ffc875c55cdecdcf4c52214007d443  kernel-source-5.15.139_smp-noarch-1.txz

Slackware x86_64 15.0 packages:
c455659e37b122e22a4b53322f6a1795  kernel-generic-5.15.139-x86_64-1.txz
97657fcdbdf707709ba8ff24266ef28d  kernel-headers-5.15.139-x86-1.txz
b02c2557d92e078e1fdc07eda2ebfcc9  kernel-huge-5.15.139-x86_64-1.txz
c97c06949033f62acb3e65b51963e2ea  kernel-modules-5.15.139-x86_64-1.txz
711156b762cb7f2b231fe98a831569a4  kernel-source-5.15.139-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.139-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.139 | 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.139-smp version when running
mkinitrd_command_generator. Note that this is only for 32-bit -- 64-bit
systems should always use 5.15.139 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.


+-----+

Slackware: 2023-325-01: Slackware 15.0 kernel Security Update

November 21, 2023
New kernel packages are available for Slackware 15.0 to fix security issues

Summary

Here are the details from the Slackware 15.0 ChangeLog: patches/packages/linux-5.15.139/*: 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.116: https://www.cve.org/CVERecord?id=CVE-2023-35788 https://www.cve.org/CVERecord?id=CVE-2022-45887 https://www.cve.org/CVERecord?id=CVE-2022-45886 https://www.cve.org/CVERecord?id=CVE-2023-3212 https://www.cve.org/CVERecord?id=CVE-2022-45919 Fixed in 5.15.117: https://www.cve.org/CVERecord?id=CVE-2023-2124 https://www.cve.org/CVERecord?id=CVE-2023-34255 Fixed in 5.15.118: https://www.cve.org/CVERecord?id=CVE-2023-3609 https://www.cve.org/CVERecord?id=CVE-2023-3117 https://www.cve.org/CVERecord?id=CVE-2023-3390 https://www.cve.org/CVERecord?id=CVE-2023-3338 Fixed in 5.15.119: https://www.cve.org/CVERecord?id=CVE-2023-3610 Fixed in 5.15.121: https://www.cve.org/CVERecord?id=CVE-2023-31248 https://www.cve.org/CVERecord?id=CVE-2023-38432 https://www.cve.org/CVERecord?id=CVE-2023-3866 https://www.cve.org/CVERecord?id=CVE-2023-2898 https://www.cve.org/CVERecord?id=CVE-2023-44466 https://www.cve.org/CVERecord?id=CVE-2023-4132 https://www.cve.org/CVERecord?id=CVE-2023-3611 https://www.cve.org/CVERecord?id=CVE-2022-48502 https://www.cve.org/CVERecord?id=CVE-2023-3865 https://www.cve.org/CVERecord?id=CVE-2023-35001 https://www.cve.org/CVERecord?id=CVE-2023-3776 https://www.cve.org/CVERecord?id=CVE-2023-3863 Fixed in 5.15.122: https://www.cve.org/CVERecord?id=CVE-2023-20593 Fixed in 5.15.123: https://www.cve.org/CVERecord?id=CVE-2023-3777 https://www.cve.org/CVERecord?id=CVE-2023-4004 Fixed in 5.15.124: https://www.cve.org/CVERecord?id=CVE-2023-4015 https://www.cve.org/CVERecord?id=CVE-2023-4147 https://www.cve.org/CVERecord?id=CVE-2023-1206 Fixed in 5.15.125: https://www.cve.org/CVERecord?id=CVE-2022-40982 https://www.cve.org/CVERecord?id=CVE-2023-20569 Fixed in 5.15.126: https://www.cve.org/CVERecord?id=CVE-2023-20588 https://www.cve.org/CVERecord?id=CVE-2023-4128 https://www.cve.org/CVERecord?id=CVE-2023-4208 https://www.cve.org/CVERecord?id=CVE-2023-4206 https://www.cve.org/CVERecord?id=CVE-2023-4207 https://www.cve.org/CVERecord?id=CVE-2023-40283 Fixed in 5.15.128: https://www.cve.org/CVERecord?id=CVE-2023-4569 https://www.cve.org/CVERecord?id=CVE-2023-39194 https://www.cve.org/CVERecord?id=CVE-2023-4273 https://www.cve.org/CVERecord?id=CVE-2023-3772 Fixed in 5.15.132: https://www.cve.org/CVERecord?id=CVE-2023-4921 https://www.cve.org/CVERecord?id=CVE-2023-4623 https://www.cve.org/CVERecord?id=CVE-2023-42753 https://www.cve.org/CVERecord?id=CVE-2023-42752 https://www.cve.org/CVERecord?id=CVE-2023-39189 https://www.cve.org/CVERecord?id=CVE-2023-4881 https://www.cve.org/CVERecord?id=CVE-2023-45871 https://www.cve.org/CVERecord?id=CVE-2023-39193 https://www.cve.org/CVERecord?id=CVE-2023-39192 Fixed in 5.15.133: https://www.cve.org/CVERecord?id=CVE-2023-42755 Fixed in 5.15.134: https://www.cve.org/CVERecord?id=CVE-2023-42754 https://www.cve.org/CVERecord?id=CVE-2023-4563 https://www.cve.org/CVERecord?id=CVE-2023-4244 https://www.cve.org/CVERecord?id=CVE-2023-5197 Fixed in 5.15.135: https://www.cve.org/CVERecord?id=CVE-2023-34324 https://www.cve.org/CVERecord?id=CVE-2023-31085 https://www.cve.org/CVERecord?id=CVE-2023-5158 Fixed in 5.15.136: https://www.cve.org/CVERecord?id=CVE-2023-35827 Fixed in 5.15.137: https://www.cve.org/CVERecord?id=CVE-2023-46813 https://www.cve.org/CVERecord?id=CVE-2023-5717 https://www.cve.org/CVERecord?id=CVE-2023-5178 (* Security fix *)

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 15.0:
Updated packages for Slackware x86_64 15.0:

MD5 Signatures

Slackware 15.0 packages: 8211588a7ce1578ea991bd5362f7445e kernel-generic-5.15.139-i586-1.txz 64037b5079bfe0757445e074c7d3c7cb kernel-generic-smp-5.15.139_smp-i686-1.txz 1a500cf7afe8e155302ac974aafa44d1 kernel-headers-5.15.139_smp-x86-1.txz ace5996456652d42f14a94c1ba36b4f1 kernel-huge-5.15.139-i586-1.txz 6069f8f4da9f93504af0298735dee9aa kernel-huge-smp-5.15.139_smp-i686-1.txz 984ad76bb952c3931e89210486466668 kernel-modules-5.15.139-i586-1.txz d0dc77021b8169ed7365130bf221e454 kernel-modules-smp-5.15.139_smp-i686-1.txz 96ffc875c55cdecdcf4c52214007d443 kernel-source-5.15.139_smp-noarch-1.txz
Slackware x86_64 15.0 packages: c455659e37b122e22a4b53322f6a1795 kernel-generic-5.15.139-x86_64-1.txz 97657fcdbdf707709ba8ff24266ef28d kernel-headers-5.15.139-x86-1.txz b02c2557d92e078e1fdc07eda2ebfcc9 kernel-huge-5.15.139-x86_64-1.txz c97c06949033f62acb3e65b51963e2ea kernel-modules-5.15.139-x86_64-1.txz 711156b762cb7f2b231fe98a831569a4 kernel-source-5.15.139-noarch-1.txz

Severity
[slackware-security] Slackware 15.0 kernel (SSA:2023-325-01)
New kernel packages are available for Slackware 15.0 to fix security issues.

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 15.0): # /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 5.15.139-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.139 | 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.139-smp version when running mkinitrd_command_generator. Note that this is only for 32-bit -- 64-bit systems should always use 5.15.139 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

News

Powered By

Footer Logo

Linux Security - Your source for Top Linux News, Advisories, HowTo's and Feature Release.

Powered By

Footer Logo