Slackware Security Advisories
Slackware Logo

News

Security Advisories

FAQ

Book

General Info

Get Slack

Install Help

Configuration

Packages

ChangeLogs

Propaganda

Ports

Other Sites

Support

Contact

Mailing Lists

About

 
From: Slackware Security Team <security@slackware.com>
To: slackware-security@slackware.com
Subject: [slackware-security] Slackware 15.0 kernel (SSA:2022-333-01)
Date: Tue, 29 Nov 2022 13:04:28 -0800 (PST)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[slackware-security]  Slackware 15.0 kernel (SSA:2022-333-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.80/*:  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.63:
    https://www.cve.org/CVERecord?id=CVE-2022-3629
    https://www.cve.org/CVERecord?id=CVE-2022-3635
    https://www.cve.org/CVERecord?id=CVE-2022-3633
    https://www.cve.org/CVERecord?id=CVE-2022-3625
    Fixed in 5.15.64:
    https://www.cve.org/CVERecord?id=CVE-2022-39190
    https://www.cve.org/CVERecord?id=CVE-2022-3028
    https://www.cve.org/CVERecord?id=CVE-2022-2905
    Fixed in 5.15.65:
    https://www.cve.org/CVERecord?id=CVE-2022-42703
    https://www.cve.org/CVERecord?id=CVE-2022-3176
    Fixed in 5.15.66:
    https://www.cve.org/CVERecord?id=CVE-2022-4095
    https://www.cve.org/CVERecord?id=CVE-2022-20421
    Fixed in 5.15.68:
    https://www.cve.org/CVERecord?id=CVE-2022-3303
    https://www.cve.org/CVERecord?id=CVE-2022-2663
    https://www.cve.org/CVERecord?id=CVE-2022-40307
    https://www.cve.org/CVERecord?id=CVE-2022-3586
    Fixed in 5.15.70:
    https://www.cve.org/CVERecord?id=CVE-2022-0171
    https://www.cve.org/CVERecord?id=CVE-2022-39842
    https://www.cve.org/CVERecord?id=CVE-2022-3061
    Fixed in 5.15.72:
    https://www.cve.org/CVERecord?id=CVE-2022-2308
    Fixed in 5.15.73:
    https://www.cve.org/CVERecord?id=CVE-2022-2978
    https://www.cve.org/CVERecord?id=CVE-2022-43750
    Fixed in 5.15.74:
    https://www.cve.org/CVERecord?id=CVE-2022-40768
    https://www.cve.org/CVERecord?id=CVE-2022-42721
    https://www.cve.org/CVERecord?id=CVE-2022-3621
    https://www.cve.org/CVERecord?id=CVE-2022-42722
    https://www.cve.org/CVERecord?id=CVE-2022-42719
    https://www.cve.org/CVERecord?id=CVE-2022-41674
    https://www.cve.org/CVERecord?id=CVE-2022-3649
    https://www.cve.org/CVERecord?id=CVE-2022-3646
    https://www.cve.org/CVERecord?id=CVE-2022-42720
    Fixed in 5.15.75:
    https://www.cve.org/CVERecord?id=CVE-2022-43945
    https://www.cve.org/CVERecord?id=CVE-2022-41849
    https://www.cve.org/CVERecord?id=CVE-2022-3535
    https://www.cve.org/CVERecord?id=CVE-2022-3594
    https://www.cve.org/CVERecord?id=CVE-2022-2602
    https://www.cve.org/CVERecord?id=CVE-2022-41850
    https://www.cve.org/CVERecord?id=CVE-2022-3565
    https://www.cve.org/CVERecord?id=CVE-2022-3542
    Fixed in 5.15.77:
    https://www.cve.org/CVERecord?id=CVE-2022-3524
    Fixed in 5.15.78:
    https://www.cve.org/CVERecord?id=CVE-2022-3628
    https://www.cve.org/CVERecord?id=CVE-2022-3623
    https://www.cve.org/CVERecord?id=CVE-2022-42896
    https://www.cve.org/CVERecord?id=CVE-2022-42895
    https://www.cve.org/CVERecord?id=CVE-2022-3543
    https://www.cve.org/CVERecord?id=CVE-2022-3564
    https://www.cve.org/CVERecord?id=CVE-2022-3619
    Fixed in 5.15.80:
    https://www.cve.org/CVERecord?id=CVE-2022-3521
    https://www.cve.org/CVERecord?id=CVE-2022-3169
  (* 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:
ftp://ftp.slackware.com/pub/slackware/slackware-15.0/patches/packages/linux-5.15.80/kernel-generic-5.15.80-i586-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware-15.0/patches/packages/linux-5.15.80/kernel-generic-smp-5.15.80_smp-i686-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware-15.0/patches/packages/linux-5.15.80/kernel-headers-5.15.80_smp-x86-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware-15.0/patches/packages/linux-5.15.80/kernel-huge-5.15.80-i586-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware-15.0/patches/packages/linux-5.15.80/kernel-huge-smp-5.15.80_smp-i686-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware-15.0/patches/packages/linux-5.15.80/kernel-modules-5.15.80-i586-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware-15.0/patches/packages/linux-5.15.80/kernel-modules-smp-5.15.80_smp-i686-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware-15.0/patches/packages/linux-5.15.80/kernel-source-5.15.80_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.80/kernel-generic-5.15.80-x86_64-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware64-15.0/patches/packages/linux-5.15.80/kernel-headers-5.15.80-x86-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware64-15.0/patches/packages/linux-5.15.80/kernel-huge-5.15.80-x86_64-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware64-15.0/patches/packages/linux-5.15.80/kernel-modules-5.15.80-x86_64-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware64-15.0/patches/packages/linux-5.15.80/kernel-source-5.15.80-noarch-1.txz


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

Slackware 15.0 packages:
b2f77a57540668f5b6f43220e7cb570e  kernel-generic-5.15.80-i586-1.txz
9db5d881a86b3078fee0129601b0d38b  kernel-generic-smp-5.15.80_smp-i686-1.txz
e5cb2079ea90fdac4cd5634e1b0c404a  kernel-headers-5.15.80_smp-x86-1.txz
f8f8dba8632644a6adc6d6d37872d9b8  kernel-huge-5.15.80-i586-1.txz
5247a51009b316ab3e740af9deac644d  kernel-huge-smp-5.15.80_smp-i686-1.txz
5ef51925119954c46a6ab2ad4b73d5f6  kernel-modules-5.15.80-i586-1.txz
664f392763d1fa36288a22fdef728b24  kernel-modules-smp-5.15.80_smp-i686-1.txz
609d4ad296b2b1bba14d1afb46de61ba  kernel-source-5.15.80_smp-noarch-1.txz

Slackware x86_64 15.0 packages:
f2a80afb7b5d3dedafb9a308ca4c6cef  kernel-generic-5.15.80-x86_64-1.txz
d5ba89c905ef386e922951525c75720e  kernel-headers-5.15.80-x86-1.txz
164206dd025c1944d4d4ccfcf72a8cf2  kernel-huge-5.15.80-x86_64-1.txz
619222efd62135d1193b222cbd645a3d  kernel-modules-5.15.80-x86_64-1.txz
8ba197539ca561c1aaba9f55ae01ed86  kernel-source-5.15.80-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.80-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.80 | 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.80-smp version when running
mkinitrd_command_generator. Note that this is only for 32-bit -- 64-bit
systems should always use 5.15.80 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 Linux Security Team
http://slackware.com/gpg-key
security@slackware.com

+------------------------------------------------------------------------+
| To leave the slackware-security mailing list:                          |
+------------------------------------------------------------------------+
| Send an email to majordomo@slackware.com with this text in the body of |
| the email message:                                                     |
|                                                                        |
|   unsubscribe slackware-security                                       |
|                                                                        |
| You will get a confirmation message back containing instructions to    |
| complete the process.  Please do not reply to this email address.      |
+------------------------------------------------------------------------+
-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAmOGYrQACgkQakRjwEAQIjO3yACePGBtcvTYnDe4a5DZtxz7yv2w
Mj0AoJADBrw3FaYuCVK3ZFlb1psILd0x
=WinD
-----END PGP SIGNATURE-----

Slackware™ is a trademark of Patrick Volkerding.