-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: kernel
Announcement ID: SUSE-SA:2006:012
Date: Mon, 27 Feb 2006 16:00:00 +0000
Affected Products: SUSE LINUX 9.3
SUSE LINUX 9.2
SUSE LINUX 9.1
SuSE Linux Desktop 1.0
SuSE Linux Enterprise Server 8
SUSE SLES 9
UnitedLinux 1.0
Vulnerability Type: various security problems
Severity (1-10): 8
SUSE Default Package: yes
Cross-References: CVE-2004-1058, CVE-2005-2553, CVE-2005-3356
CVE-2005-3358, CVE-2005-3623, CVE-2005-3808
CVE-2005-3847, CVE-2005-3848, CVE-2005-3858
CVE-2005-4605
Content of This Advisory:
1) Security Vulnerability Resolved:
various kernel security problems
Problem Description
2) Solution or Work-Around
3) Special Instructions and Notes
4) Package Location and Checksums
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
none
6) Authenticity Verification and Additional Information
______________________________________________________________________________
1) Problem Description and Brief Discussion
The Linux kernel has been updated to fix various security problems.
All SUSE Linux versions and products are affected, the exact affected
versions are listed per entry. A SUSE Linux 10.0 kernel update was
released 2 weeks ago, also fixing the issues listed in here. (SUSE
Linux Enterprise Server is abbreviated as SLES, Novell Linux Desktop as NLD,
and Open Enterprise Server as OES).
- CVE-2005-3623: Remote users could set ACLs even on read-only
exported NFS filesystems and so circumvent access control.
Affected: All SUSE Linux based products.
- CVE-2004-1058: A race condition was fixed which could allow
local users to read environment variables of another process.
This is a reissue of an earlier fix in the 2.6 kernel also present
in the 2.4 kernel.
SUSE Linux Enterprise Server 8 and SUSE Linux Desktop 1 are affected.
- CVE-2005-2553: Fixed an oops when a 64bit binary was traced with
a 32bit ltrace.
This problem only affects SLES 8 for x86-64.
- CVE-2005-3356: A double decrement in mq_open system call could lead
to local users crashing the machine.
This problem affects SUSE Linux 9.1 up to 9.3, SLES 9, and NLD 9
and OES.
- CVE-2005-3358: A 0 argument passed to the set_mempolicy() system
call could lead to a local user crashing the machine.
This problem affects SUSE Linux 9.1 up to 9.3, SLES 9, and NLD 9
and OES.
- CVE-2005-3848: A dst_entry leak in the icmp_push_reply could be
used to exhaust system memory. However this problem happens only
on machines which are already nearly memory starved.
This problem affects SUSE Linux 9.1 up to 9.3, SLES 9, and NLD 9
and OES.
- CVE-2005-3858: A memory leak in the ip6_input_finish function
in ip6_input.c might allow attackers to cause a denial of service
via malformed IPv6 packets with unspecified parameter problems,
which prevents the SKB from being freed.
This problem affects SUSE Linux 9.1 up to 9.3, SLES 9, and NLD 9
and OES.
- CVE-2005-4605: Kernel memory could be leaked to user space through a
problem with seek() in /proc files .
This problem only affects SUSE Linux 9.2 and 9.3
- CVE-2005-3847: The handle_stop_signal function in signal.c allows
local users to cause a denial of service (deadlock) by sending a
SIGKILL to a real-time threaded process while it is performing a
core dump.
This problem only affects SUSE Linux 9.3.
- CVE-2005-3808: A 32 bit integer overflow on 64bit mmap calls
could be used by local users to hang the machine.
This problem only affects SUSE Linux 9.3.
A number of additional non-security bugs were fixed, but are not listed here.
Please check the separate maintenance information mails or the RPM changelogs
(with rpm ---changelog -q name-of-kernel-rpm).
2) Solution or Work-Around
There is no known workaround, please install the update packages.
3) Special Instructions and Notes
SPECIAL INSTALLATION INSTRUCTIONS
================================ The following paragraphs guide you through the installation
process in a step-by-step fashion. The character sequence "****"
marks the beginning of a new paragraph. In some cases, the steps
outlined in a particular paragraph may or may not be applicable
to your situation. Therefore, make sure that you read through
all of the steps below before attempting any of these
procedures. All of the commands that need to be executed must be
run as the superuser 'root'. Each step relies on the steps
before it to complete successfully.
Note that usually it is sufficient to just run YaST Online Update
to correctly update the kernel. Only if you are using manually
changed bootloader configurations manual steps are necessary.
**** Step 1: Determine the needed kernel type.
Use the following command to determine which kind of kernel is
installed on your system:
rpm -qf --qf '%{name}\n' /boot/vmlinuz
**** Step 2: Download the packages for your system.
Download the kernel RPM package for your distribution with the
name indicated by Step 1. Starting from SUSE LINUX 9.2, kernel
modules that are not free were moved to a separate package with
the suffix '-nongpl' in its name. Download that package as well
if you rely on hardware that requires non-free drivers, such as
some ISDN adapters. The list of all kernel RPM packages is
appended below.
The kernel-source package does not contain a binary kernel in
bootable form. Instead, it contains the sources that correspond
with the binary kernel RPM packages. This package is required to
build third party add-on modules.
**** Step 3: Verify authenticity of the packages.
Verify the authenticity of the kernel RPM package using the
methods as listed in Section 6 of this SUSE Security
Announcement.
**** Step 4: Installing your kernel rpm package.
Install the rpm package that you have downloaded in Step 2 with
the command
rpm -Uhv
replacing with the filename of the RPM package
downloaded.
Warning: After performing this step, your system may not boot
unless the following steps have been followed
completely.
**** Step 5: Configuring and creating the initrd.
The initrd is a RAM disk that is loaded into the memory of your
system together with the kernel boot image by the boot loader.
The kernel uses the content of this RAM disk to execute commands
that must be run before the kernel can mount its root file
system. The initrd is typically used to load hard disk
controller drivers and file system modules. The variable
INITRD_MODULES in /etc/sysconfig/kernel determines which kernel
modules are loaded in the initrd.
After a new kernel rpm has been installed, the initrd must be
recreated to include the updated kernel modules. Usually this
happens automatically when installing the kernel rpm. If
creating the initrd fails for some reason, manually run the
command
/sbin/mkinitrd
**** Step 6: Update the boot loader, if necessary.
Depending on your software configuration, you either have the
LILO or GRUB boot loader installed and initialized on your
system. Use the command
grep LOADER_TYPE /etc/sysconfig/bootloader
to find out which boot loader is configured.
The GRUB boot loader does not require any further action after a
new kernel has been installed. You may proceed to the next step
if you are using GRUB.
If you use the LILO boot loader, lilo must be run to
reinitialize the boot sector of the hard disk. Usually this
happens automatically when installing the kernel RPM. In case
this step fails, run the command
/sbin/lilo
Warning: An improperly installed boot loader will render your
system unbootable.
**** Step 7: Reboot.
If all of the steps above have been successfully completed on
your system, the new kernel including the kernel modules and the
initrd are ready to boot. The system needs to be rebooted for
the changes to be active. Make sure that all steps have been
completed then reboot using the command
/sbin/shutdown -r now
Your system will now shut down and restart with the new kernel.
4) Package Location and Checksums
The preferred method for installing security updates is to use the YaST
Online Update (YOU) tool. YOU detects which updates are required and
automatically performs the necessary steps to verify and install them.
Alternatively, download the update packages for your distribution manually
and verify their integrity by the methods listed in Section 6 of this
announcement. Then install the packages using the command
rpm -Fhv
to apply the update, replacing with the filename of the
downloaded RPM package.
x86 Platform:
SUSE LINUX 9.3:
726987fcb2e29a3e6e8d413c1a5dfe1d
c543d65d53d4169e734c058020d567ec
b37dc9424cf567c7736e7ae319e73562
de248d731063686bc283beafa031b537
6d193d0deaf3777821849cc61802ff65
5eb3a6dc960720d8d93cde49ec7700f8
9f6a944e6f901072d6ce48fbaa1290f0
62ab0ddbcc4e3d01090b7b5fafd38d8a
7f73075bdd31464db500d644b97edc81
02486777b820d02b425fed71a4c5019f
15dfaf2802842860f478f171eda39af1
1f9636bf36fddc76aaf057651a45309e
1078b4a0182fe0c4cec06c9547fb1a9e
78c81eb9d6c5779343c3e29e81030308
61fbfde10f475ea4c0d724d87d63501f
19a7f29a385995702ac30407be70d6d2
SUSE LINUX 9.2:
73fa6376eb84222b2fffa6483eab7afc
6c81a75b8fec4b14fc9e4365c187f00d
aa22cc2a3d959f790ec8523e4019c747
3890821a67d7d60ffff0caffc2cab778
7511e2f0934af8eae4bb3179e7840fbd
7117c43424009f3c2eb2921e8fbc95ed
c1d885bfb6675ae69e3b1692f5fc946a
05236f7ce1b52ab54961ad527ce805e7
7dc21ec2ccd8dbe4e5d87b41c836bbaf
f8ce8a36267968fc939a0ee2599e157e
2e9cfb9aef2447aa952f527eded19c24
0b131a3243a8b6afd9a8e945b1af2fd4
1f3c40dc3cf9438fefeeb5eab8d4197e
aace00350fb0297a2f028699b4668697
SUSE LINUX 9.1:
d6b302c940c8430fab37d9aa9a5e1214
785040d76717cd8083e256000b7f63d5
5a6544c2a26a3a3dc155198138eaa83f
02711564583edfb898433c549b09bd7d
b5703b2f2546e67b1d0ff984a4293cd0
591e787dda803b499e6c10d25e05b770
0b55769312b026a1b9cd4bae2c391d98
266fd61aeb1861dc076d445117f66baf
c1627d9ba295289524d174e13610f09b
8e6287ab9fcc3992fb49afadc797da45
Platform Independent:
SUSE LINUX 9.3:
cb887f584a0c8f8b37638bab10407d73
SUSE LINUX 9.2:
62a62a57d97af0ee27a1d9e2f1b5477b
SUSE LINUX 9.1:
936c10c7337f5d6bfde60066fd457989
d8ee9fb3b0423be9ced1e4c2e7de8f05
x86-64 Platform:
SUSE LINUX 9.3:
e8bd3166ade78e0f33ba7a065add24ba
e6ec8fd3780b20bf49bf261d10d4423e
73382acf65787d53973ca779bf0579cc
27527e2d10b6b37243009d61ff2ff6f8
45e2b2428d73e4367f03eb9841b7074e
db2912ac4b3e7ba4cac7d5eb0e3120f5
SUSE LINUX 9.2:
88ed9d91a4414f7f4e39e899ca7a7ef4
5425d91d11a695b36415384be9536cf9
8670c9bc84d9a4d493e4b18aee1c29b2
b340a89c163944042c0a214795a3ad7b
66b91efb196d3461d29d90ba8e19c747
2f3a689fb2e5e286e15e573739828d99
SUSE LINUX 9.1:
7b99fc2ceef67fd5e23b22b325f2dcd4
1e7e270cbbd76e8af428f7dd7c59d2b8
c60de58a4feed20754aa202bc5545149
9dff984bb8294fac593591db3f5ff9df
8cfefc4446f2fc70e5fcbae2b1c5e8b9
097429f49530fddbed45f3122a66f91a
Sources:
SUSE LINUX 9.3:
18dba7c11f866a58e39a12e79319be85
a9374b06cca86ce9a8373c43c17ac9e4
b25622507b1903ef0f3bf848839ce08d
c9381f3813e7af4fa9cf4cc9ce5621ff
9b83f383688e1e2cddc5a40c3bda99d4
4ad088fa0b6607c5d7fce5d0fad1ae52
47b05b06a6676e2b781e648e37dc69b0
f551a23519fbf78341cb67ec4724982f
a0885202b09e6b10e392707111f58942
dd70e4bf36e779f4b17adb1736dc8f35
5f7c7741a6adc9dc5100eeadbdf2f7c6
SUSE LINUX 9.2:
52499e0c322a0ca5c5cf90893cf0b0d1
9f34cf79d1700bcd0c0f1058ef247edb
840876249319d785e5cc45e5bf1490c8
6cb3fc2605a81385726b77aad68e9e4a
8dacc62d42fc39a483da38fa08a1276d
29c05920ac9106aad6d6d030ff6fca7b
3af6d2ffea1c50db219e990665d81a56
9be5e2ab15164b15e494b11f53f6118d
17eea8abe7a7bb2f6fc7c029e05be7a2
16b975dfc87624197e50d840657f8751
SUSE LINUX 9.1:
4b79dc800753b16483f304a6511ce8bf
30182af29f0f23b90c0fe14005a730a9
bc02096441207893cf47d2be7c8b06ea
9e3601a5dbc80c014e54281709e0fe61
5f4f416be9c8a82930187001970a6d1c
1d3eb0c88355dab211f708e6cc8e54e0
21e6098484c4dcec2601dd08b945b308
c2008e98d134ba1566a782dd122ebd8a
4581214c4fea38c7524465361a68e57c
72f1beb412f7e1ca417de9f1e7569304
976703d007470f12a822da6ce664d129
e99e2496532756559fd5c67ee283df40
0c4edc9be7a9fb28c0b59d6117982b0a
c4e2f55f248e850f1bd7ec16ce17b6a7
784c069db96b17f32b10cd0673c41a92
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
______________________________________________________________________________
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
none
______________________________________________________________________________
6) Authenticity Verification and Additional Information
- Announcement authenticity verification:
SUSE security announcements are published via mailing lists and on Web
sites. The authenticity and integrity of a SUSE security announcement is
guaranteed by a cryptographic signature in each announcement. All SUSE
security announcements are published with a valid signature.
To verify the signature of the announcement, save it as text into a file
and run the command
gpg --verify
replacing with the name of the file where you saved the
announcement. The output for a valid signature looks like:
gpg: Signature made using RSA key ID 3D25D3D9
gpg: Good signature from "SuSE Security Team "
where is replaced by the date the document was signed.
If the security team's key is not contained in your key ring, you can
import it from the first installation CD. To import the key, use the
command
gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc
- Package authenticity verification:
SUSE update packages are available on many mirror FTP servers all over the
world. While this service is considered valuable and important to the free
and open source software community, the authenticity and the integrity of
a package needs to be verified to ensure that it has not been tampered
with.
There are two verification methods that can be used independently from
each other to prove the authenticity of a downloaded file or RPM package:
1) Using the internal gpg signatures of the rpm package
2) MD5 checksums as provided in this announcement
1) The internal rpm package signatures provide an easy way to verify the
authenticity of an RPM package. Use the command
rpm -v --checksig
to verify the signature of the package, replacing with the
filename of the RPM package downloaded. The package is unmodified if it
contains a valid signature from build@suse.de with the key ID 9C800ACA.
This key is automatically imported into the RPM database (on
RPMv4-based distributions) and the gpg key ring of 'root' during
installation. You can also find it on the first installation CD and at
the end of this announcement.
2) If you need an alternative means of verification, use the md5sum
command to verify the authenticity of the packages. Execute the command
md5sum
after you downloaded the file from a SUSE FTP server or its mirrors.
Then compare the resulting md5sum with the one that is listed in the
SUSE security announcement. Because the announcement containing the
checksums is cryptographically signed (by security@suse.de), the
checksums show proof of the authenticity of the package if the
signature of the announcement is valid. Note that the md5 sums
published in the SUSE Security Announcements are valid for the
respective packages only. Newer versions of these packages cannot be
verified.
- SUSE runs two security mailing lists to which any interested party may
subscribe:
suse-security@suse.com
- General Linux and SUSE security discussion.
All SUSE security announcements are sent to this list.
To subscribe, send an e-mail to
.
suse-security-announce@suse.com
- SUSE's announce-only mailing list.
Only SUSE's security announcements are sent to this list.
To subscribe, send an e-mail to
.
For general information or the frequently asked questions (FAQ),
send mail to or
.
==================================================================== SUSE's security contact is or .
The public key is listed below.
====================================================================
