| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <alpine.LNX.2.02.1608291818580.4446@connie.slackware.com>
Date: Mon, 29 Aug 2016 18:19:16 -0700 (PDT)
From: Slackware Security Team <security@...ckware.com>
To: slackware-security@...ckware.com
Subject: [slackware-security] kernel (SSA:2016-242-01)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[slackware-security] kernel (SSA:2016-242-01)
New kernel packages are available for Slackware 14.1 to fix a security issue.
Here are the details from the Slackware 14.1 ChangeLog:
+--------------------------+
patches/packages/linux-3.10.103/*: Upgraded.
A flaw was found in the implementation of the Linux kernels handling of
networking challenge ack where an attacker is able to determine the shared
counter. This may allow an attacker located on different subnet to inject
or take over a TCP connection between a server and client without having to
be a traditional Man In the Middle (MITM) style attack.
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:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5389
(* 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 14.1:
ftp://ftp.slackware.com/pub/slackware/slackware-14.1/patches/packages/linux-3.10.103/kernel-generic-3.10.103-i486-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware-14.1/patches/packages/linux-3.10.103/kernel-generic-smp-3.10.103_smp-i686-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware-14.1/patches/packages/linux-3.10.103/kernel-headers-3.10.103_smp-x86-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware-14.1/patches/packages/linux-3.10.103/kernel-huge-3.10.103-i486-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware-14.1/patches/packages/linux-3.10.103/kernel-huge-smp-3.10.103_smp-i686-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware-14.1/patches/packages/linux-3.10.103/kernel-modules-3.10.103-i486-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware-14.1/patches/packages/linux-3.10.103/kernel-modules-smp-3.10.103_smp-i686-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware-14.1/patches/packages/linux-3.10.103/kernel-source-3.10.103_smp-noarch-1.txz
Updated packages for Slackware x86_64 14.1:
ftp://ftp.slackware.com/pub/slackware/slackware64-14.1/patches/packages/linux-3.10.103/kernel-generic-3.10.103-x86_64-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware64-14.1/patches/packages/linux-3.10.103/kernel-headers-3.10.103-x86-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware64-14.1/patches/packages/linux-3.10.103/kernel-huge-3.10.103-x86_64-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware64-14.1/patches/packages/linux-3.10.103/kernel-modules-3.10.103-x86_64-1.txz
ftp://ftp.slackware.com/pub/slackware/slackware64-14.1/patches/packages/linux-3.10.103/kernel-source-3.10.103-noarch-1.txz
MD5 signatures:
+-------------+
Slackware 14.1 packages:
1121a215f3af597c87fc18aa7d04cef1 kernel-generic-3.10.103-i486-1.txz
8aee03c88e4fca95302b6350df2ec13f kernel-generic-smp-3.10.103_smp-i686-1.txz
15f50b5ece93f19db77118dcb19692d5 kernel-headers-3.10.103_smp-x86-1.txz
8bd94dc6dd24ecc980bf75aabffcce5f kernel-huge-3.10.103-i486-1.txz
4f59f96b3053a6fdf31a7a82b78c941e kernel-huge-smp-3.10.103_smp-i686-1.txz
04a521fd17b3d03c91242c9f11dc0447 kernel-modules-3.10.103-i486-1.txz
2a7505fd7508b9b19759b614141f7996 kernel-modules-smp-3.10.103_smp-i686-1.txz
10ad031b1aafb3ceb94f391ba467a419 kernel-source-3.10.103_smp-noarch-1.txz
Slackware x86_64 14.1 packages:
7136915c953b60a52fb7732998789fcc kernel-generic-3.10.103-x86_64-1.txz
26dc0f2b6adcbebd25716d7d249c78bc kernel-headers-3.10.103-x86-1.txz
4b03d7d4b3b117258d0813d6b87320c4 kernel-huge-3.10.103-x86_64-1.txz
b4a5b76fd4536b32a7f6d21b3cb4a53d kernel-modules-3.10.103-x86_64-1.txz
16cbbf92568c22ef1023457dab1666ab kernel-source-3.10.103-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:
# /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 3.10.103-smp | bash
For a 64-bit machine, or a 32-bit uniprocessor machine, use this command:
# /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 3.10.103 | 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 3.10.103-smp version when running
mkinitrd_command_generator. Note that this is only for 32-bit -- 64-bit
systems should always use 3.10.103 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@...ckware.com
+------------------------------------------------------------------------+
| To leave the slackware-security mailing list: |
+------------------------------------------------------------------------+
| Send an email to majordomo@...ckware.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-----
iEYEARECAAYFAlfEvdAACgkQakRjwEAQIjOilQCfWWq09EWnJUYwSvJvj68rZ7Ar
bwUAn0501tA1wkRZgSbu9hQI+OSYWuGD
=pShs
-----END PGP SIGNATURE-----
Powered by blists - more mailing lists