-----BEGIN PGP SIGNED MESSAGE-----
______________________________________________________________________________
SUSE Security Announcement
Package: kernel
Announcement-ID: SUSE-SA:2005:021
Date: Mon, 04 Apr 2005 12:00:00 +0000
Affected products: 8.2, 9.0, 9.2
SUSE Linux Desktop 1.0
SUSE Linux Enterprise Server 8
Vulnerability Type: local privilege escalation
Severity (1-10): 6
SUSE default package: yes
Cross References: CAN-2005-0750
Content of this advisory:
1) security vulnerability resolved:
local root exploit in bluetooth network stack
problem description
2) solution/workaround
3) special instructions and notes
4) package location and checksums
5) pending vulnerabilities, solutions, workarounds:
See SUSE Security Summary Report.
6) standard appendix (further information)
______________________________________________________________________________
1) problem description, brief discussion
This Linux kernel security update fixes a problem within the Bluetooth
kernel stack which can be used by a local attacker to gain root access or
crash the machine.
To exploit this problem, the Bluetooth modules do not need to be
loaded since they are auto loaded on demand (except in products mentioned
below).
This problem has been assigned the Mitre CVE ID CAN-2005-0750.
Updated packages have been provided for the default affected products:
- SUSE Linux 8.2, 9.0 and 9.2 (both i386 and x86_64) - SUSE Linux
Enterprise Server 8 (i386, ia64 and x86_64) - SUSE Linux Desktop 1.0
Other architectures do not have Bluetooth enabled.
Also SUSE Linux 9.1, SUSE Linux Enterprise Server 9 and Novell Linux
Desktop 9 are not affected by default since the Bluetooth module is not
auto loaded. These will get the patch with the next security update.
2) solution/workaround
Please install the updated packages.
A workaround is to disable Bluetooth by using:
- Remove or move away the bluetooth core module.
On 2.6 kernels this is the file:
/lib/modules//kernel/net/bluetooth/bluetooth.ko
On 2.4 kernels this is the file:
/lib/modules//kernel/net/bluetooth/bluez.o
- Disable auto load of the bluetooth protocol module by commenting
out the line:
alias net-pf-31 bluez
in /etc/modules.conf (2.4 systems) or the line:
alias net-pf-31 bluetooth
in /etc/modprobe.conf (2.6 systems).
Make sure the module is not loaded, or run "rmmod bluetooth" /
"rmmod bluez".
3) special instructions and notes
SPECIAL INSTALL INSTRUCTIONS:
============================= The following paragraphs will 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, please make sure to read through all of the steps below
before attempting any of these procedures.
All of the commands that need to be executed are required to be
run as the superuser (root). Each step relies on the steps before
it to complete successfully.
**** Step 1: Determine the needed kernel type
Please use the following command to find the kernel type that is
installed on your system:
rpm -qf /boot/vmlinuz
Following are the possible kernel types (disregard the version and
build number following the name separated by the "-" character)
k_deflt # default kernel, good for most systems.
k_i386 # kernel for older processors and chip sets
k_athlon # kernel made specifically for AMD Athlon(tm) family processors k_psmp # kernel for Pentium-I dual processor systems
k_smp # kernel for SMP systems (Pentium-II and above)
k_smp4G # kernel for SMP systems which supports a maximum of 4G of RAM
kernel-64k-pagesize
kernel-bigsmp
kernel-default
kernel-smp
**** Step 2: Download the package for your system
Please download the kernel RPM package for your distribution with the
name as indicated by Step 1. The list of all kernel rpm packages is
appended below. Note: The kernel-source package does not
contain a binary kernel in bootable form. Instead, it contains the
sources that the binary kernel rpm packages are created from. It can be
used by administrators who have decided to build their own kernel.
Since the kernel-source.rpm is an installable (compiled) package that
contains sources for the linux kernel, it is not the source RPM for
the kernel RPM binary packages.
The kernel RPM binary packages for the distributions can be found at the
locations below .
8.2/rpm/i586
9.0/rpm/i586
9.1/rpm/i586
9.2/rpm/i586
After downloading the kernel RPM package for your system, you should
verify the authenticity of the kernel rpm package using the methods as
listed in section 3) of each SUSE Security Announcement.
**** Step 3: Installing your kernel rpm package
Install the rpm package that you have downloaded in Steps 3 or 4 with
the command
rpm -Uhv --nodeps --force
where is the name of the rpm package that you downloaded.
Warning: After performing this step, your system will likely not be
able to boot if the following steps have not been fully
followed.
**** Step 4: configuring and creating the initrd
The initrd is a ramdisk that is loaded into the memory of your
system together with the kernel boot image by the bootloader. The
kernel uses the content of this ramdisk to execute commands that must
be run before the kernel can mount its actual root filesystem. It is
usually used to initialize SCSI drivers or NIC drivers for diskless
operation.
The variable INITRD_MODULES in /etc/sysconfig/kernel determines
which kernel modules will be loaded in the initrd before the kernel
has mounted its actual root filesystem. The variable should contain
your SCSI adapter (if any) or filesystem driver modules.
With the installation of the new kernel, the initrd has to be
re-packed with the update kernel modules. Please run the command
mk_initrd
as root to create a new init ramdisk (initrd) for your system.
On SuSE Linux 8.1 and later, this is done automatically when the
RPM is installed.
**** Step 5: bootloader
If you run a SUSE LINUX 8.x, SLES8, or SUSE LINUX 9.x system, there
are two options:
Depending on your software configuration, you have either the lilo
bootloader or the grub bootloader installed and initialized on your
system.
The grub bootloader does not require any further actions to be
performed after the new kernel images have been moved in place by the
rpm Update command.
If you have a lilo bootloader installed and initialized, then the lilo
program must be run as root. Use the command
grep LOADER_TYPE /etc/sysconfig/bootloader
to find out which boot loader is configured. If it is lilo, then you
must run the lilo command as root. If grub is listed, then your system
does not require any bootloader initialization.
Warning: An improperly installed bootloader may render your system
unbootable.
**** Step 6: reboot
If all of the steps above have been successfully completed on your
system, then the new kernel including the kernel modules and the
initrd should be ready to boot. The system needs to be rebooted for
the changes to become active. Please make sure that all steps have
completed, then reboot using the command
shutdown -r now
or
init 6
Your system should now shut down and reboot with the new kernel.
4) package location and checksums
Please download the update package for your distribution and verify its
integrity by the methods listed in section 3) of this announcement.
Then, install the package using the command "rpm -Fhv file.rpm" to apply
the update.
Our maintenance customers are being notified individually. The packages
are being offered to install from the maintenance web.
x86 Platform:
SUSE Linux 9.2:
83cf3ebb75d4e1a7e435dd13ee2d8d1c
0fb1469b42bf62e5cc87cb4f1410ef09
9.2/rpm/i586/kernel-bigsmp-nongpl-2.6.8-24.14.i586.rpm
970d200f0f0abd9025f858abc575c5b7
9.2/rpm/i586/kernel-default-2.6.8-24.14.i586.rpm
ba4fdb46b50cd7b09824cbedc61bfc8c
9.2/rpm/i586/kernel-default-nongpl-2.6.8-24.14.i586.rpm
20d97e2d55dc5433f70e02e270ba13c5
600ce2e1f6fe06d2db4f0f4bdf1797b6
ed5aaf51f97ae8a8e7bd0992e6982a69
9.2/rpm/i586/kernel-source-2.6.8-24.14.i586.rpm
0dd5cffcda797bbdd4cbee53f5a5d05d
d74094729d1046f491e36950d3155d26
e37de6a488da1887ae1f8eee94ceeef3
81b454e91fde4128b9185aafd9012666
9.2/rpm/i586/ltmodem-8.31a8-6.7.i586.rpm
2c8bc429e498cd79f9528847efcd0c08
0f31340cd661a5e8c9fa04068e2c5097
f80c2529732a36436cc16fed1a5214bb
9.2/rpm/noarch/kernel-docs-2.6.8-24.14.noarch.rpm
a92ea90e592e9e7a5c1a953c69963010
SUSE Linux 9.0:
2245daa3986b2befb607e0ca71dfb818
ef15111940735dd59964d2356fad9daf
d24065275f61694a7a241c7782b60a8d
1480147c870224583cfc8047f6cc8827
0924f45e191c17a0fd18868f25d661af
72683d1de2eff870248794f3617e2f0d
9.0/rpm/i586/k_um-2.4.21-286.i586.rpm
183a596c6c7a61aac6f477c67f9d31f8
52b637e3f0ab4c715ccba423b7560604
960a99f0100ff6ef63d538c0be693130
source rpm(s):
2abdcc2913cb35d6c63aa60436cf317a
66cbb800b7f7a7c272db41a09d85ca06
795048442b07da36f9615364a4d4776f
9.0/rpm/src/k_deflt-2.4.21-286.src.rpm
ef1ad2e167cb18e730d2203cfc4cc79a
7649239b72c5ef11e5af2a54de1f9112
fc6e4f0553621438ccc950d60d4ae95a
14934af7134d786d5229c9ca7793ac0c
9.0/rpm/src/kernel-source-2.4.21-286.src.rpm
feb614d9a26cebce682ebfcc695c19ab
0e8609ae41f93d7e23e69fb5ba426ca8
SUSE Linux 8.2:
8.2/rpm/i586/k_athlon-2.4.20-133.i586.rpm
820c50323c4e7f529fc045c25320db33
8.2/rpm/i586/k_deflt-2.4.20-133.i586.rpm
e9fffc1da0665f6634622e57ebdd2d56
8.2/rpm/i586/k_psmp-2.4.20-133.i586.rpm
679a02afce5b9514bcf0b8499a29bc82
717bf34a3641a5bf0f8ccf26990442d2
8.2/rpm/i586/kernel-source-2.4.20.SuSE-133.i586.rpm
79ad972a1204c25fa5b8722500f1cbe3
source rpm(s):
0641b2ad5043d15f4d21dd8d59337b07
c9345e663d84eddca48b7260b509ef10
c3caebe80385586f79e0ac4bb2b7099b
0161fd5bb0b97af8d33dbfbf39cb3f89
8.2/rpm/src/kernel-source-2.4.20.SuSE-133.src.rpm
d896e620182157894085729ea98e0e40
x86-64 Platform:
SUSE Linux 9.2:
9.2/rpm/x86_64/kernel-default-2.6.8-24.14.x86_64.rpm
00daf3e5ccda0243add47e6b31d3b324
9.2/rpm/x86_64/kernel-default-nongpl-2.6.8-24.14.x86_64.rpm
000e1ebe2effe50862866c4bb895b6b1
9.2/rpm/x86_64/kernel-smp-2.6.8-24.14.x86_64.rpm
24a87872b72f82569cc48b4e4937625e
6678d95a894a6068556a0679fe2804c4
9243499a1e2d3d187b03e9648efedc9a
4e6efe583cb0b017bf74fbc31cf0f4ec
source rpm(s):
9.2/rpm/src/kernel-default-2.6.8-24.14.nosrc.rpm
2ec696edcbbcee3467506185cdff6cde
9.2/rpm/src/kernel-smp-2.6.8-24.14.nosrc.rpm
706bdd002d12f682536b63ad92ca3c35
254a7e8f8284539862309249767819fc
1c3bd22089eff61c8a9fc27e15b5d569
SUSE Linux 9.0:
494a414468b1b4ab035610b749f8c7fa
d60ae1bf9a4fdfcf0d2adfc15dbecf2b
b2575d169b38f1058176874919dbbb63
source rpm(s):
b9a11390529505e1c824bdea4d5eecec
562198014fbdf598f131510cefe14d47
99e2df1ec59dfa89c18077465cd63660
______________________________________________________________________________
5) Pending vulnerabilities in SUSE Distributions and Workarounds:
See SUSE Security Summary Report.
______________________________________________________________________________
6) standard appendix: authenticity verification, additional information
- Package authenticity verification:
SUSE update packages are available on many mirror ftp servers all over
the world. While this service is being considered valuable and important
to the free and open source software community, many users wish to be
sure about the origin of the package and its content before installing
the package. 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) md5sums as provided in the (cryptographically signed) announcement.
2) using the internal gpg signatures of the rpm package.
1) 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
announcement. Since the announcement containing the checksums is
cryptographically signed (usually using the key security@suse.de),
the checksums show proof of the authenticity of the package.
We disrecommend to subscribe to security lists which cause the
email message containing the announcement to be modified so that
the signature does not match after transport through the mailing
list software.
Downsides: You must be able to verify the authenticity of the
announcement in the first place. If RPM packages are being rebuilt
and a new version of a package is published on the ftp server, all
md5 sums for the files are useless.
2) 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, where is the
filename of the rpm package that you have downloaded. Of course,
package authenticity verification can only target an un-installed rpm
package file.
Prerequisites:
a) gpg is installed
b) The package is signed using a certain key. The public part of this
key must be installed by the gpg program in the directory
~/.gnupg/ under the user's home directory who performs the
signature verification (usually root). You can import the key
that is used by SUSE in rpm packages for SUSE Linux by saving
this announcement to a file ("announcement.txt") and
running the command (do "su -" to be root):
gpg --batch; gpg < announcement.txt | gpg --import
SUSE Linux distributions version 7.1 and thereafter install the
key "build@suse.de" upon installation or upgrade, provided that
the package gpg is installed. The file containing the public key
is placed at the top-level directory of the first CD (pubring.gpg)
and at .
- SUSE runs two security mailing lists to which any interested party may
subscribe:
suse-security@suse.com
- general/linux/SUSE security discussion.
All SUSE security announcements are sent to this list.
To subscribe, send an email 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 email to
.
For general information or the frequently asked questions (faq)
send mail to:
or
respectively.
==================================================================== SUSE's security contact is or .
@suse.de>.
The public key is listed below.
====================================================================
