Share your story
The central voice for Linux and Open Source security news
Home News Topics Advisories HOWTOs Features Newsletters About Register

Sign up!
EnGarde Community
What is the most important Linux security technology?
Linux Events
Linux User Groups
Link to Us
Security Center
Book Reviews
Security Dictionary
Security Tips
White Papers
Featured Blogs
All About Linux
DanWalsh LiveJournal
Latest Newsletters
Linux Advisory Watch: March 27th, 2015
Linux Security Week: March 23rd, 2015
LinuxSecurity Newsletters
Choose Lists:
About our Newsletters
RSS Feeds
Get the LinuxSecurity news you want faster with RSS
Powered By

SuSE: various kernel problems Print E-mail
User Rating:      How can I rate this item?
Posted by Joe Shakespeare   
SuSE Several vulnerabilities have been found and fixed in the Linux kernel.


                        SUSE Security Announcement

        Package:                kernel
        Announcement-ID:        SUSE-SA:2004:044
        Date:                   Tuesday, Dec 21st 2004 18:00 MEST
        Affected products:      SUSE Linux 8.1, 8.2, 9.0, 9.1, 9.2
                                SUSE Linux Enterprise Server 8, 9
                                SUSE Linux Desktop 1.0
                                Novell Linux Desktop 9
        Vulnerability Type:     local privilege escalation
                                remote denial of service
                                local denial of service
        Severity (1-10):        9
        SUSE default package:   yes
        Cross References:       CAN-2004-1068

    Content of this advisory:
        1) security vulnerability resolved:
             - several vulnerabilities in the linux kernel
           problem description
        2) solution/workaround
        3) special instructions and notes
        4) package location and checksums
        5) pending vulnerabilities, solutions, workarounds:
            - problem with smbfs in earlier update
            - see SUSE Security Summary Report
        6) standard appendix (further information)

1) problem description, brief discussion

    Linux kernel

        Several vulnerabilities have been found and fixed in the Linux

        Paul Starzetz reported that the missing serialization in
        unix_dgram_recvmsg() which was added to kernel 2.4.28 can
        be used by a local attacker to gain elevated privileges (root
        access). This issue is tracked by the Mitre CVE ID CAN-2004-1068.

        Paul Starzetz and Georgi Guninski reported independently that bad
        argument handling and bad integer arithmetics in the IPv4 sendmsg
        handling of control messages could lead to a local attacker crashing
        the machine.
        This problem was fixed by Herbert Xu and is tracked by the Mitre
        CVE ID CAN-2004-1016.

        Georgi Guninski reported a memory leak in the IP option handling
        of the IPv4 sendmsg call.

        Paul Starzetz found bad handling in the kernel IGMP code, which
        could lead to a local attacker being able to crash the machine.
        This problem was fixed by Chris Wright and is tracked by the Mitre
        CVE ID CAN-2004-1137.

        Olaf Kirch found and fixed a problem in the RPC handling in the
        which could lead to a remote attacker crashing the machine.

        A local denial of service problem in the aio_free_ring system call
        could allow a local attacker to crash the machine.

        A problem in the memory management handling of ELF executables could
        lead to a local attacker crashing the machine with a handcrafted
        ELF binary. (This is a VMA overlap problem and not related to
        earlier ELF problems.)

        A buffer overflow in the system call handling in the 32bit system
        call emulation on AMD64 / Intel EM64T systems was fixed. It is not
        thought to be exploitable.

        A memory leak in the ip_conntrack_ftp firewalling module was fixed
        in the 2.6 kernels.

        Various UML security issues in the SUSE Linux 9.2 UML setup
        were fixed.

        Additionally some non-security bugs were fixed in the released

        SUSE Linux Enterprise Server 8 and SUSE Linux 8.1:
        - A memory leak in addition / removal of SCSI target devices was

        - A race condition in SCSI I/O accounting which could lead to
          erroneous reports on SCSI disk I/O was fixed.

        - S390: Patches from IBM have been installed in the S/390
          architecture, both for 32 and 64bit.
          Refer to the maintenance information mail for the full change log.

        - The "memfrac" and "lower_zone_reserve" kernel parameters had
          no effect since they were used before kernel command line parsing.

        - PowerPC: Missing synchronization that could lead to processes
          hanging in signal delivery was added.

        SUSE Linux Enterprise Server 9 and SUSE Linux 9.1:
        - A vfree() was called with interrupts disabled in the SCSI generic
          device handling, which could lead to a hanging machine.

        - A race condition between a file unlink and umount could lead to a
          machine crash.

        - Fixed a small memory leak in bio_copy_user().

        - cdrecord -scanbus could crash the kernel when using the "gdth" SCSI

        - Allow reading from zero page (/dev/zero) using O_DIRECT/rawio.

        - Fixed some LSB issues in the fcntl compatibility handling.

        - The st (SCSI tape) driver did not pass on generic SCSI ioctl
          commands to the SCSI mid layer.

        SUSE Linux 9.2:
        - The kernel installation routines did not call depmod for the modules
          in the -nongpl RPMs, so they could not be loaded.
          This lead to non working USB modem drivers and similar.
          This problem was fixed.

        - A Problem with mounting iPods over FireWire was fixed.

        - A data corruption problem in the megaraid driver was fixed.

        - A pageattr overflow condition in the memory subsystem
          and missing TLB flush if multiple pages were passed were fixed.

        - Allow reading from zeropage with O_DIRECT/rawio.

        - Do not restart the system on ACPI events after power down.
          (Make it no longer start on opening the lid of just shutdown
           laptops for instance.)

        - New memory imbalance handling handling by Andrea leading
          to better Out Of Memory (OOM) handling was added.

2) solution/workaround

    Please install the fixed packages, there is no workaround.

3) special instructions and notes

    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

  **** 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


    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

    If you run SUSE LINUX 8.1 and haven't applied the kernel update
    (SUSE-SA:2003:034), AND you are using the freeswan package, you also
    need to update the freeswan rpm as a dependency as offered
    by YOU (YaST Online Update). The package can be downloaded from

  **** 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
        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:
    patch rpm(s):
    source rpm(s):

    SUSE Linux 9.1:
    source rpm(s):

    SUSE Linux 9.0:
    source rpm(s):

    SUSE Linux 8.2:
    source rpm(s):

    SUSE Linux 8.1:
    source rpm(s):

    x86-64 Platform:

    SUSE Linux 9.2:
    source rpm(s):

    SUSE Linux 9.1:
    source rpm(s):

    SUSE Linux 9.0:
    source rpm(s):

5)  Pending vulnerabilities in SUSE Distributions and Workarounds:

    Please see our Security Summary Report.

    - problem with smbfs in the previous kernel update

      We received reports of smbfs being broken by our last kernel
      update (released on Dec 1st, SUSE-SA:2004:042).

      This apparently only affects the smbfs filesystem on 2.6 kernels,
      so SUSE Linux 9.1, 9.2, SUSE Linux Enterprise Server 9 and Novell
      Linux Desktop 9.

      This problem is unfortunately not yet fixed in this security
      update, we will be releasing fixed packages in the begin of next

      As workaround please change to use the cifs filesystem if
      possible, which replaces smbfs in the 2.6 kernel series.


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,
       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.
        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 "" 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
        -   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  or .
    The  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 
pub  1024D/9C800ACA 2000-10-19 SuSE Package Signing Key 

< Prev   Next >


Latest Features
Peter Smith Releases Linux Network Security Online
Securing a Linux Web Server
Password guessing with Medusa 2.0
Password guessing as an attack vector
Squid and Digest Authentication
Squid and Basic Authentication
Demystifying the Chinese Hacking Industry: Earning 6 Million a Night
Free Online security course (LearnSIA) - A Call for Help
What You Need to Know About Linux Rootkits
Review: A Practical Guide to Fedora and Red Hat Enterprise Linux - Fifth Edition
Yesterday's Edition
Partner Sponsor

Community | HOWTOs | Blogs | Features | Book Reviews | Networking
 Security Projects |  Latest News |  Newsletters |  SELinux |  Privacy |  Home
 Hardening |   About Us |   Advertise |   Legal Notice |   RSS |   Guardian Digital
(c)Copyright 2015 Guardian Digital, Inc. All rights reserved.