-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: kernel
Announcement ID: SUSE-SA:2005:029
Date: Thu, 09 Jun 2005 11:00:00 +0000
Affected Products: 8.2, 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
Vulnerability Type: local privilege escalation
Severity (1-10): 7
SUSE Default Package: yes
Cross-References: CAN-2005-0400
CAN-2005-0749
CAN-2005-0750
CAN-2005-0756
CAN-2005-1263
CAN-2005-1762
CAN-2005-1763
CAN-2005-1764
CAN-2005-1765
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:
- when creating directories on ext2 filesystems the kernel did not
zero initialize the memory allocated. Therefore potentially
sensitive information could be exposed to users (CAN-2005-0400).
All SUSE LINUX based products are affected.
- local users can crash the kernel via a crafted ELF library or
executable, which causes a free of an invalid pointer
(CAN-2005-0749).
All SUSE LINUX based products are affected.
- local users could gain root access via a bluetooth socket
(CAN-2005-0750).
The fix for this problem was missing in SUSE LINUX 9.3 only.
- local users could gain root access by causing a core dump of
specially crafted ELF executables (CAN-2005-1263).
The problem is believed to be not exploitable on any SUSE LINUX
based product. The patch is included nevertheless.
- on the x86-64 platform various bugs allowed local users to crash
the kernel or CPU (CAN-2005-0756, CAN-2005-1762, CAN-2005-1764,
CAN-2005-1765)
All SUSE LINUX based products on the x86-64 architecture are
affected.
- an overflow in the x86-64 ptrace code allowed local users to
write a few bytes into kernel memory pages they normally
shouldn't have access to (CAN-2005-1763).
SLES 9 and SUSE LINUX 9.1-9.3 on the x86-64 architecture are
affected.
- insufficient checks in the 32bit DRM ioctl functions could allow
unprivileged local users to gain root access.
SLES 9 and SUSE LINUX 9.1-9.3 on the x86-64 architecture are
affected.
2) Solution or Work-Around
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:
5078f73bd890915709bd38b4ced9959e
1e39110ede66b924ceb4d0ce953a3ff7
c0e36b69d5f652f8c09ba95ef251dd54
31a9e85ab40f92fec04acf61c4be475c
6edc8fb5503fdae343b8d927718ec43f
c49a3e0363c4ef231665612b5eb96838
680683a88100de073eab8d7eab60c030
e8e95d4541fc695f6427a69fed32fd98
0063999d2b49d214b77d195e8e74bc5d
f0a318a4a2948f18bbe152f9812926ed
f69fba2cd4be1b2385ca1147bf00cdc5
7472d83fe70ce0698c5bf27f579f717f
5969c90b9e160f327648ed92a539179f
e920b54ef527916f4dd8cd7e792da638
3f917596d28c0443018599de2579bd1f
609755b992bd6f0b799d9c8f7a6be9c1
b5a3cfcb38952f7c30a3bddf3566592c
663985e94c0db55ea4981080cd7a02cb
SUSE Linux 9.2:
c57684a254c9196452791211c2d2e623
14f110ad0d1584a05b1cdea9ffc22d87
c64c3cd402dfdf2e54da5920556bcadb
0f5544eba423cb9686ae72cab58a6d39
3489493426039cd2326261f952571010
9a39a337ceb4cb92469d3ded0c3ca129
2771cc636378aa6c2a0612077826847c
668523e1493198fac27e33ad7f28bcf0
50100dda60c29c6bb5be251f28e96075
a1e4c6bcd72a8c5d7bd5a24fbbc311f6
805d7f82fc83d2ffcece30c5a674298a
1d5763e65fb3d3a29829d1055d24ff7e
149a83cff156d5b3174245ca0d649d94
31f471cac4d4f44001f6b09106f0ee29
d220a4ee181c7fecc3bfc149fc0f9f5b
SUSE Linux 9.1:
a9309114199d6f979aaec615afd52ebb
61bd4e56acb2efbc61c986b67d7e1438
6689cc0e3193bbec8b86677c3db70d10
d4b93a7fbc4f8d49b0b6b8051659fe44
9b35f3a64cdec3f5d7ebfc3cf6ab0c34
4c6ad23c98cd1258e3fcc221115a790d
1620b1222e1b64b79e7d91e2c63be58f
source rpm(s):
ccec411ce27dc7d85434815ce57d4aff
abac6185c5bd8cea873a4a0db9e9d53d
a2bf969bfb6ed215cdfa01c47b1a8b0a
da8a27b1cf6529264b4437bb9f4ac2ea
bc79bd4ccf62e168dbc101e66673f464
bde63208fe2c1a6bcf0db7ba3745f317
83ba7017e9c3935b2db63f51215d15ea
SUSE Linux 9.0:
f1ff84299d504068a47d64f04ecc1f5e
aa6cd21af0bc3f12e9b81f2112b75e27
9ab7fed216c7b966a1764e7a9cda43b8
93c91911fe6a7ce7275ee8c6a96b4c19
ba736936d48609bcd963f7c77ff33e80
2ba65158e3bbc3f0ff07f373b9ef453a
1acf3de9e1dd2a496ded4ef084cf8d03
869a07e6ba013d1a21d6fd0e794c9c51
20e9aeb94f090e34dbd3c71e1e00628e
source rpm(s):
9314bc6d43be7fd79d93ef83abd6fae9
4e43e63276fcdc2d2e1b7e91669456f1
495ee067f8ee4b0d8f779876e419bcca
c960e653a4cc01fc82463a0aecc0dd99
fa0601b1fb6e23ace6ae6e5acbaf4132
01e0bde3d24459f2bebb4c34cad5bbea
8e9214137a0cd03000457af2a29bd834
e59d1bcee85f750554d4f6ff12e7207c
60ef251418dfb767ccbfddfcf3961c3e
SUSE Linux 8.2:
c24836022715429f83ba3ff35aabe5b4
c46fecf63621d1cd90ec4c87ca4051d4
d577ee9a967438748d9da9df622e6821
9aec15f4aaf79e20674f62e624b24a41
eb2ec983f099436c99814baafcbd715c
source rpm(s):
a5d43f8e8b062a511f015740f1d8bfa8
f05cca5373393df03fc1fa60baf9ff1a
a0cffaf8231c468f632f6d7f8df09b58
b9705b55e99094a1e962c3a8b5a6ad49
4b921845db68a4b8ff8b9ece53762813
x86-64 Platform:
SUSE Linux 9.3:
7e87431c3e61b7d52fe06e36fcc2e82d
144112d2164428dd906f11ea10a54d5e
6bd66c1887a7927102e17153ece2e75c
e256ee95d9a9e8b0fab9e7b7ed249ff7
d8746a9ca87fc91c2de5daaa621b82a4
c565248800d560fe3f7478a237831ffd
source rpm(s):
0245359048c50e2dfa1e5abe4837f924
5c5c737264c34a0aa260cc4494633f96
87e4fb10ff7081df52a472d8f839f953
83e9b376fdd7e7a120424db25ba5c783
SUSE Linux 9.2:
680d4a0b155ddd1c2e4920a90784d7a3
b1499074310e9c39e0780b8668396365
259e74a406717a03564aa9fcc22b20be
7b4ba1455d5ff293f64fbe7bd161b432
e0cc9281b31a64d0b12910cccfcbba77
0397704ea1340231e95af4c1cf784369
source rpm(s):
42daaf0124e8e4bd45abbdb323bb9767
e1a5c17be8a6462c5bc620dbb8797b02
ecc10a8d79694e0444bfc16e722396da
48af4a5ae79bcdb07e9c942bc7ff70a1
SUSE Linux 9.1:
475cafdeedcbfb5d769733b416168f74
258d045cb69c0c63716b5ed3eedde8f7
d3db1dc3230f8f182d764046fbffc2e2
da1f1f869abadf128149fddec471cd73
c47befa7a0fa11d54f6232c504f41ed0
source rpm(s):
bdefeb522554feaeb268a748845b6447
2a980cc7a259c13da695d69864229963
11a527f29426bde6dbe8340222bb2622
ec3e423f83f966c1fa1aaabf4e8e864d
ea66541b5fcee73c57e0cdae2057bf6d
SUSE Linux 9.0:
25737de4d2740b56293819ab8560faf3
2129f7523033f88b08e1836a17e7de55
f5d8a23c421dee3f83af0a30aee5e952
source rpm(s):
061942b579f080d5d9dd34f91cbda832
bab2c96013632d60cec6dcd4a38de3bc
e52bc3293ae049a8c81577d527964b06
______________________________________________________________________________
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.
====================================================================
