-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: kernel
Announcement ID: SUSE-SA:2005:044
Date: Thu, 04 Aug 2005 08:00:00 +0000
Affected Products: 9.0, 9.1, 9.2, 9.3
SUSE Linux Desktop 1.0
SUSE Linux Enterprise Server 8, 9
Novell Linux Desktop 9
Open Enterprise Server 9
Vulnerability Type: local privilege escalation
Severity (1-10): 7
SUSE Default Package: yes
Cross-References: CAN-2005-1761
CAN-2005-1767
CAN-2005-1768
Content of This Advisory:
1) Security Vulnerability Resolved:
several 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:
- see SUSE Security Summary Report
6) Authenticity Verification and Additional Information
______________________________________________________________________________
1) Problem Description and Brief Discussion
The Linux kernel is the core component of the Linux system.
This update fixes various security as well as non-security problems
discovered since the last round of kernel updates.
Not all kernels are affected by all the problems, each of the problems
has an affected note attached to it.
The CAN-YYYY-NNNN IDs are Mitre CVE Candidate IDs, please see
http://www.mitre.org for more information.
The following security problems have been fixed:
- local users could crash the system by causing stack fault
exceptions (CAN-2005-1767)
SUSE Linux 9.0 and SLES8 are affected.
- local users could use ptrace to crash the kernel
(CAN-2005-1761).
SLES8 on the ia64 architecture is affected.
- by causing an overflow in the 32bit execve function users could
crash the kernel or even execute code (CAN-2005-1768).
SLES 9 on the x86-64 and ia64 architectures and SUSE Linux 9.1
on the x86-64 architecture are affected.
- an overflow when validating XDR data for the nfsacl protocol
could crash the kernel.
SUSE Linux 9.2 and 9.3 are affected.
- local users could crash the kernel by reading from large
offsets in sysfs files
SUSE Linux 9.2 is affected.
On SUSE Linux 9.1 this update contains the kernel used by the
SUSE Linux Enterprise Server 9, Service Pack 2. This kernel adds
among many bugfixes and driver updates support for non-executable
pages (NX) on x86 CPUs and improves dual core CPU support.
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.
**** 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.
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web.
x86 Platform:
SUSE Linux 9.3:
05a238ad052efca5071097cdc915df17
bfeb0c950feeaa75c79a4a57cc87f551
ebf02e94b3c2ec1026a55e25373f8116
542f4ccc7e75110569e10ab477d31dc5
72dd929e09d816a765465bc9c3ab9ce3
656b7c959ee5306740cc8f22ce6d82a7
42582b11fffd615eb29670e4f85601ee
73d4f9dca2fb4dda5f696a085e7b2055
d3a123fcfdbd7325fd8df02010d8092a
e1d4701ada55009074f0716b52de3c71
94b16ac6039c5acf9ed6839bd3a42e5e
2be56cc3c69f259e1bc1069a80886d00
2d1da7bd73fe7b7281b6f3da75866f1e
5188ad0125447cb5dc7d9d890661aff6
dc2f268a8d34608a398a072b0828894d
bea2f498ef755159877132808fcc67b4
4e43301928440f85de5416becaf4dd80
0d1daffc2d7e0d94f994ee260be87cc4
SUSE Linux 9.2:
0d8d7462b5d396c9aeec58879f41ace3
0eaaa279a6dd6b9e1a01be9a05d978fb
e3653101d73a0bede0ac40b4fa29d9dc
f795ecb51ef90a0bb241ea4e6bbc3bba
e322aa000bed8e34db575a0db6bd72a7
6ae5087a6026c40d8abc1e5d3c9d79ed
07ab3b8e2fe7566efe7745042e36b869
bc27ddec86fab10c92a626ccc9b52125
9996748f30aa51f3f7edc2bb57bf33f0
ec997c83e8b8f5ff1237b824333a03a6
73f6f4c7b2573612d7bdc218900bd259
8bb6fb7a7bb16d5dcfa546eb166cd0a5
5e94647cfa4a9ea1bb051160ce469a8d
a724edf0312eac59fe79620e83c4875b
a0a2b0320011b726a8333566986c0adf
SUSE Linux 9.1:
cc7d96f52dd7c0764c692dc13fd53cec
e386360521fb20a2e538fbfbded5a811
d7af0f43d7f7244715ce0b08c801e949
cbd5fe9db7294b3f59b22e7b4305c68d
b09fc2db0298d8cddc7f563f5c70c72a
6bede3ceed177c7d878fc7da3f86a324
c1cf2903606be5a12bad9f1eab2eae81
77f4fe83be8c81f88117ec52521ffe81
source rpm(s):
3a1b93dc227e264b3dd4facbfa14e1ef
cfea9bd165db64ced6293308812ea4ee
6a92646a4271ccf3478a10ea1926de6d
bc2ee08fd05f1bc8d60b49d767f0f513
1a3a88bc0618b78353de3e2947f28979
e7f672c81b506567857e90ddfd820c7f
89687a12bb4c32f724f2297fc503af7d
53003b04f9b047e9e9b23f0e93d7750f
SUSE Linux 9.0:
1bae954d54dc935445c4d759ec4781c6
f33a23b16531dbb31e86235aecea5af0
f36353243bc41416484ac3b83b99cf54
9c38ed804c03d68e9140b048efed0d1b
f0adf768e915c3af251828b7b31fc9aa
5a13e58bb1210a4e908655eb176c0fb8
6d48fec139aadda5d471cf4c7e1b9f0b
e3768ecf5b9ac848976cabef5fb3809a
3fd2674fce2a1d50072dc22f254872bc
source rpm(s):
359859f0c2cb8f827adb1dcdb37e07a5
c44cc10e6d607229244ec17cdc6e3684
fc16ff423a1e61efe5bf540f6238540a
704de65cefa1879236ef9e422ca15829
bc6d49efe5f3586ee387440ab8549fab
09833f9243a18d534e2c436a97253b45
8ac4b4cf7dd9c8fb231c5039e53f1cfd
11151763f415842946ee60325ee01d3c
febc3670da245f8d78bb89a006765d35
x86-64 Platform:
SUSE Linux 9.3:
cfaefcc7e6a70ab33b14407f1b65f80a
31c72377eea1d62a1e7acd59549e92ec
e28191a62427f1804ce96ad3ff84e65f
99078de1a8b126aa7f10dcffee178d15
76a2eabf1217625e7daf12140b2eec13
f608f35bdb90e29f8b2f7b0d9ebe55ad
source rpm(s):
0026116fa23db0619bec4c1cad7131bc
687dc52d024ef4c29e0d8215ec06f43f
d66859bc79ced127079cee1a58227d90
2df4bab28340ed5beea7cc641b37996f
SUSE Linux 9.2:
c25dff3ebb63aa965967c3134b46044c
2f431403b235eb60cb5aac4e2cfb0129
c26d75ff5551d8cf96e9d0c76e103eed
4651a609fe14cb138d1338baf037a446
79d4e5e9943057b18363964c106ed68b
9087ce46d4533afc3665d9270ccb15d4
source rpm(s):
93789c90324bd74589d188ca28bb90fb
cd29ff98ea1e4966e9ef9728f31550c0
0fd3efc9a17a8a6dd4ba4412f156001d
ca8ed47420d9dd89e632934f9ea3c7e3
SUSE Linux 9.1:
9e55e1c6ad4224a6aba51f7e8e741f64
8f11a22c99a750c75dab36e76f4a2258
1c5ac7a96d946e7102b81f2899be001b
808e3ee17e3be2e3eab1f2570326690a
a62089a8df14b58353cd35ff554f47fb
31fbf23ab758e9a7b1253e15aae2bf50
source rpm(s):
d6284bac1d04f9bc4b6133a2a2af527c
51c2c136a047595ff3e16b5b9e7e6718
8672f0b590d95373fec4aefb6a065161
5e47cb20a39df305cb8055e40ed57b51
6291bb3e37b8ae990e7c2b1454bfd407
58e7f56bf7dcc95db8b893775a7b5322
SUSE Linux 9.0:
f91b1ea439a0d2246b66c38c401b6356
d35d0e61e2fc4573364f1d796957c684
e60dc4818a39287185fe1bd90611e0ed
source rpm(s):
ec45006a680174e5fb1335efebedc63b
f2ada5581d73c90298150b29e870527b
f57382aa59ae24eda94255eb52edb4b6
______________________________________________________________________________
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
- see SUSE Security Summary Report
______________________________________________________________________________
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.
====================================================================
