|| ||Marcus Meissner <email@example.com>|
|| ||[suse-security-announce] SUSE Security Announcement: kernel bugfixes and SP1 merge
|| ||Fri, 04 Feb 2005 18:01:35 +0100|
-----BEGIN PGP SIGNED MESSAGE-----
SUSE Security Announcement
Date: Friday, Feb 4th 2005 18:00 MET
Affected products: SUSE Linux 9.1
SUSE Linux Enterprise Server 9
Vulnerability Type: critical bugs
Severity (1-10): 6
SUSE default package: yes
Content of this advisory:
1) security vulnerability resolved:
- Merged various security fixes from previous kernel update
- SUSE Linux 9.1 kernel upgraded to SLES 9 Service Pack 1
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
The linux kernel is the core of the SUSE Linux based products.
Two weeks ago we released the Service Pack 1 for our SUSE Linux
Enterprise Server 9 product. Due to the strict code freeze we were
not able to merge all the security fixes from the last kernel update
on Jan23rd (SUSE-SA:2005:003) into this kernel.
This update merges those missed security fixes and also included critical
bug fixes for the SP1 kernel.
Other SUSE Linux versions are not included in this update.
For our SUSE Linux 9.1 Box customers this update includes an
upgrade of the kernel to the kernel level we use with SUSE Linux
Enterprise Server 9 + Service Pack 1.
Changes for SUSE Linux Enterprise Server 9 customers:
The following security bugs were fixed for the Service Pack 1 kernel:
- A NFS Direct I/O local denial of service could allow a local attacker
to crash the machine.
- A previous smbfs security fix was faulty, writes did no longer work
on smbfs shares.
- Unsigned vs signed problems in the generic SCSI ioctl handler were
reported by grsecurity. They have no impact due to the compiler
using unsigned arithmetic, but are fixed nevertheless.
- ppos /proc file race conditions in the mapped_base and oom_adjust proc
files were fixed.
Also following critical bugs were fixed:
- A bug in the pciconfig sysfs interface could cause incorrect values to
be read from and written to PCI config space.
- A locking problem in CKRM could lead to a crash.
- In low memory situations, large writes would not be serviced in a
- The initialization of the bio->bi_bdev field was incorrect.
- VFS callouts for flock were added.
- MD on top of Device Mapper based devices was not working and lead to
- Non-fatal errors encountered during read ahead operations caused the
device mapper multipath to fail the hardware path.
- A race condition in the kernel timer code could lead to kernel crashes
under high load.
- An inetaddr notification problem with SCTP could lead to machine
For SUSE Linux 9.1 customers additionally the Service Pack 1
kernel changes apply (long list):
Platform / Hardware / Driver support
* Introduce concept of "cloned" drivers to minimize impact
on HW certifications
In cases where updating driver would have impacted too
many hardware certifications we introduced a cloned
driver which supports only the new PCI IDs by default.
* Support many new hardware components via driver and PCI
+ cloned tg3-new with version 3.10 to support
Broadcom 5721 and 5751
+ cloned bcm-new with version 7.3.5 to support
+ updated e1000-new with version 5.3.19 to support
one new PCI ID
+ updated ixgb to version 1.0.82 to support 10 GB
+ updated ipr to version 22.214.171.124 to support new RAID
+ updated IBM ServeRAID driver ips to 7.10.18 to fix
+ updated s2io driver to version 126.96.36.199
+ updated qlogic to version 8.00.00 to use official
release which is better and binary compatible to
version 8.00.00b14 which was used in SLES 9 GA.
+ updated megaide to version 5.07r to support LSI
+ updated megaraid_mbox to version 188.8.131.52/184.108.40.206
for new hardware support
+ updated cciss driver to version 2.6.4 to support
+ updated gdth to version 3.04 for new hardware
+ updated Emulex lpfc driver to version 2.10g for
+ added driver jsm version 1.1 to support Digi Neo
PCI serial cards
+ updated avm_fcdsl driver to support Fritz!Card DSL
USB analog driver and Fritz!Card DSL USB 2.0 driver
+ updated avmfritzcapi to support new Eumex devices
+ included support for Intel i915 chipset (hwinfo,
+ enhanced driver update dialog to also support USB
+ fixed 4-port SATA support in the ICH6 driver
+ updated MPT fusion driver to version 3.01.14.23
+ fixed aic7?xx driver probe info
+ added Altix system controller communication driver
+ cloned aic79xx-new with version 2.0.12 to support
AIC7901 and 39320
+ added Qlogic iSCSI support (qla4xxx)
+ added patches to Infiniband Gen1 code
+ back ported dpt_i2o from 2.6.8
+ updated aacraid driver to version 1.1.2-lk2 from
+ added TIO support for SGI Altix
* allow modules to use virtual IRQs
* e1000 EEH error must not remove device
* fix bad cciss unknown ioctl return
* update e1000 drivers according to new information from
* fix veth dying on ppc64
* fix oops in e1000 driver on x86_64
* fix oops with Nvidia Nforce4
* enable APIC on ES7000 architecture and increase
* fix oops with gdth controller on x86_64
* enable new DASD CCW IDs (S/390)
* fix some hipersockets bugs and a dasd dbf oops on s390
Filesystems and I/O subsystem
* Fixed files > 2 GB in isofs
* Merged new Lustre hooks
* Updated XFS filesystem and tools to latest CVS snapshot
* Updated CIFS to 1.22
* Improved iSCSI and SAN/NAS support with patches from
EMC, NetAPP and others
* Back ported several NFS bug fixes from upstream/mainline
* Integrated patches to allow enabling ext3 reservation
* fix file locking for 32 bit apps running on 64 bit
* improve NFS performance by avoiding unnecessary
* allow swapfiles > 2G on x86
* fix reiserfs oops on small file systems (< 128 MB)
* fix panic and deadlock in XFS direct IO
* allow reading from zeropage with O_DIRECT/rawio
* add reiserfs performance improvements
* fix ACL umask handling over nfs
* add several autofs4 fixes
* infiniband can also be used on ppc64
* fix oops in aio_free_ring
* fix spinlock problem in infiniband drivers
* fix ext2/ext3 memory leak
* Fix ext3 directIO when extending the journal
* kernel statd should accept NOTIFY calls from high ports
* Added multipath fixes for barrier handling
* With SP1 we now disabled by default the multipathing
fail over support in the QLogic driver as it caused many
problems. We print a warning that it is depreciated and
how one can still turn it on if needed using
* Provide code to enable recovery from PCI EEH errors
* Added CPU hotplug support for S/390
* Added powernow K8 cpufreq support for CG stepping K8
* Added cpufreq support for SMP systems
* fix centrino speedstep on x86-64
* Integrated bugfix to SHPC PCI hotplug driver
* Updated CKRM to E16 and added CPU controller
* Updated kdb to version 4.4
* Updated Linux kernel crash dump (lkcd) and lkcdutils
* Added SGI Altix hardware performance monitoring API
* Exported some symbols needed by ES7000 Service Processor
* Added tg3 ethtool stats
* Added modular kdb support for x86_64
* Added PAGG support on IPF
* fix problem with monitored processes going to sleep on
* correctly display per process CPU utilization
* fix double echo on x86-64 KDB
* check PROM version on ia64 Altix machines and print
* update CKRM to newer revision
* fix breakpoints on x86-64 KDB
* allow for producing reliable backtraces with lkcd
Scalability / Performance
* Improved RCU scalability
* Fixed scalability problem in dnotify_parent
* Assorted scalability improvement for large machines
* Support SGI Altix and 512 CPUs with Linux kernel crash
* Added CPUSET support for IPF
* Added scalability enhancements for big IPF machines
* Added support for systems with many IRQ resources
* Added clustered APIC support for x86_64
* Default readahead to 512KB (instead of 128KB)
* fix TPC-C performance problems on x86_64 (caused by
* don't waste memory for hashes on huge machines
* fix possible cpuset race
* avoid memory allocation problem on machines where still
enough memory is available
* allow memory holes on S/390
* enlarge max number of CPUs on x86-64 and number of
* Disable clustered APIC mode on AMD systems
* fix perfmon assertion failure in pfm_load_regs
* Back ported epoll fixes from 2.6.9
* Integrated numerous other bugfixes from
* Several backports from upstream/mainline kernel:
+ unmap_mapping_range() from 2.6.6
+ generic_file_direct_write() and
generic_file_buffered_write() from 2.6.9-rc4
+ backport mapping_mapped()
+ export sync_page_range
* Support official variable name INSTALL_MOD_DIR in
addition to our MOD_DIR
* Fixed hooks to enable CA
* Added kernel support for POSIX message queue
* fix sys_stime() in 31-bit compatibility mode on S/390
* fix CD/DVD writing for non-root users
* fix device special files and permission cache
* fix problem with pclose() sometimes hanging
* crbce should provide time stamp in msec rather than in
* allow IRQ0 to be used as a legal PCI device IRQ
* fix possible EEH or memory corruption when DMA crosses a
* fix iSeries Linux on legacy systems not reporting PURR
* do not create unnamed directory under /rcfs/taskclass
* fix hang caused by loopback TX
* limit max number of concurrent khelper processes
* allow ACPI PCI hotplug callbacks to
* fix IMM highmem oops
* avoid deadlocks with non-ram under mlockall
* always add credentials to inodes for NFS
* fix race condition in unix_dgram_recvmsg()
* fix vfree() with interrupts disabled in sg driver
* do not fill up process table when many events occur
* fix MCA during cross-partition MPI (ia64)
* fix random kernel memory corruption if openfirmware
stdin device is an usb controller
* Fix CPU time reporting for single processes
* fix kernel hang in __getblk_slow()
* sunrpc - don't crash on unknown program numbers
* fix memory leak in pageattr code (x86 and x86-64 only)
* fix RAID1 device failure resulting in kernel crash
* don't lose edge triggered IRQ when delivered while IRQ
* fix USB HID driver parsing usage IDs
* allow keyboard to survive if any key (e.g. F2) is
No workaround is available. Please install the updated packages.
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 chipsets
k_athlon # kernel made specifically for AMD Athlon(tm) family
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
**** 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 ftp://ftp.suse.com/pub/suse/i386/update/.
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
rpm -Uhv --nodeps --force <K_FILE.RPM>
where <K_FILE.RPM> 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
**** 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
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
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
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
**** 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
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
Our maintenance customers are being notified individually. The packages
are being offered to install from the maintenance web.
SUSE Linux 9.1:
SUSE Linux 9.1:
5) pending vulnerabilities in SUSE Distributions and Workarounds:
Please see the 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
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 firstname.lastname@example.org),
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
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 <file.rpm>
to verify the signature of the package, where <file.rpm> is the
filename of the rpm package that you have downloaded. Of course,
package authenticity verification can only target an un-installed rpm
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 "email@example.com" 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 ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de .
- SUSE runs two security mailing lists to which any interested party may
- general/linux/SUSE security discussion.
All SUSE security announcements are sent to this list.
To subscribe, send an email to
- 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:
SUSE's security contact is <firstname.lastname@example.org> or <email@example.com>.
The <firstname.lastname@example.org> public key is listed below.
The information in this advisory may be distributed or reproduced,
provided that the advisory is not modified in any way. In particular,
it is desired that the clear-text signature shows proof of the
authenticity of the text.
SUSE Linux AG makes no warranties of any kind whatsoever with respect
to the information contained in this security advisory.
Type Bits/KeyID Date User ID
pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team <email@example.com>
pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <firstname.lastname@example.org>
- -----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.0.7 (GNU/Linux)
- -----END PGP PUBLIC KEY BLOCK-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
-----END PGP SIGNATURE-----
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
to post comments)