-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: kernel
Announcement ID: SUSE-SA:2009:017
Date: Fri, 03 Apr 2009 12:00:00 +0000
Affected Products: SLE SDK 10 SP2
SUSE Linux Enterprise Desktop 10 SP2
SUSE Linux Enterprise 10 SP2 DEBUGINFO
SUSE Linux Enterprise Server 10 SP2
Vulnerability Type: remote denial of service
Severity (1-10): 7
SUSE Default Package: yes
Cross-References: CVE-2008-1294, CVE-2009-0028, CVE-2009-0065
CVE-2009-0675, CVE-2009-0676, CVE-2009-1046
Content of This Advisory:
1) Security Vulnerability Resolved:
Linux kernel security update
Problem Description
2) Solution or Work-Around
3) Special Instructions and Notes
4) Package Location and Checksums
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
Please see the SUSE Security Summary Report.
6) Authenticity Verification and Additional Information
______________________________________________________________________________
1) Problem Description and Brief Discussion
The Linux kernel for SUSE Linux Enterprise 10 Service Pack 2 was
updated to fixes various bugs and several security issues.
Following security issues were fixed:
CVE-2009-0675: The skfp_ioctl function in drivers/net/skfp/skfddi.c
in the Linux kernel permits SKFP_CLR_STATS requests only when the
CAP_NET_ADMIN capability is absent, instead of when this capability
is present, which allows local users to reset the driver statistics,
related to an "inverted logic" issue.
CVE-2009-0676: The sock_getsockopt function in net/core/sock.c in
the Linux kernel does not initialize a certain structure member,
which allows local users to obtain potentially sensitive information
from kernel memory via an SO_BSDCOMPAT getsockopt request.
CVE-2009-0028: The clone system call in the Linux kernel allows
local users to send arbitrary signals to a parent process from an
unprivileged child process by launching an additional child process
with the CLONE_PARENT flag, and then letting this new process exit.
CVE-2008-1294: The Linux kernel does not check when a user attempts
to set RLIMIT_CPU to 0 until after the change is made, which allows
local users to bypass intended resource limits.
CVE-2009-0065: Buffer overflow in net/sctp/sm_statefuns.c in the
Stream Control Transmission Protocol (sctp) implementation in the
Linux kernel allows remote attackers to have an unknown impact via
an FWD-TSN (aka FORWARD-TSN) chunk with a large stream ID.
CVE-2009-1046: The console selection feature in the Linux kernel when
the UTF-8 console is used, allows physically proximate attackers to
cause a denial of service (memory corruption) by selecting a small
number of 3-byte UTF-8 characters, which triggers an an off-by-two
memory error. It is is not clear if this can be exploited at all.
Also a huge number of regular bugs were fixed, please see the RPM
changelog for full details.
2) Solution or Work-Around
There is no known workaround, please install the update packages.
3) Special Instructions and Notes
Please reboot the machine after installing the update.
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:
SUSE Linux Enterprise Desktop 10 SP2 for AMD64 and Intel EM64T
https://login.microfocus.com/nidp/app/login;keywords=1f9272102cdb11fea73949ffdb5ba881
SUSE Linux Enterprise 10 SP2 DEBUGINFO for IBM zSeries 64bit
https://login.microfocus.com/nidp/app/login;keywords=2167d7c3381356f1edd1695673f5b5e3
SUSE Linux Enterprise 10 SP2 DEBUGINFO for IBM POWER
https://login.microfocus.com/nidp/app/login;keywords=8c191558bacc4e54ae26ddcf21d10f9f
SUSE Linux Enterprise 10 SP2 DEBUGINFO for IPF
https://login.microfocus.com/nidp/app/login;keywords=d70827089b862762d58e4a5f83a612df
SUSE Linux Enterprise Server 10 SP2
https://login.microfocus.com/nidp/app/login;keywords=1f9272102cdb11fea73949ffdb5ba881
https://login.microfocus.com/nidp/app/login;keywords=2167d7c3381356f1edd1695673f5b5e3
https://login.microfocus.com/nidp/app/login;keywords=8c191558bacc4e54ae26ddcf21d10f9f
https://login.microfocus.com/nidp/app/login;keywords=d70827089b862762d58e4a5f83a612df
https://login.microfocus.com/nidp/app/login;keywords=fa9be097c78c2f4acb003b27ea5b6cce
SLE SDK 10 SP2
https://login.microfocus.com/nidp/app/login;keywords=1f9272102cdb11fea73949ffdb5ba881
https://login.microfocus.com/nidp/app/login;keywords=8c191558bacc4e54ae26ddcf21d10f9f
https://login.microfocus.com/nidp/app/login;keywords=d70827089b862762d58e4a5f83a612df
https://login.microfocus.com/nidp/app/login;keywords=fa9be097c78c2f4acb003b27ea5b6cce
SUSE Linux Enterprise 10 SP2 DEBUGINFO
https://login.microfocus.com/nidp/app/login;keywords=1f9272102cdb11fea73949ffdb5ba881
https://login.microfocus.com/nidp/app/login;keywords=8c191558bacc4e54ae26ddcf21d10f9f
https://login.microfocus.com/nidp/app/login;keywords=d70827089b862762d58e4a5f83a612df
https://login.microfocus.com/nidp/app/login;keywords=fa9be097c78c2f4acb003b27ea5b6cce
SUSE Linux Enterprise Desktop 10 SP2
https://login.microfocus.com/nidp/app/login;keywords=1f9272102cdb11fea73949ffdb5ba881
https://login.microfocus.com/nidp/app/login;keywords=fa9be097c78c2f4acb003b27ea5b6cce
SUSE Linux Enterprise Desktop 10 SP2 for x86
https://login.microfocus.com/nidp/app/login;keywords=fa9be097c78c2f4acb003b27ea5b6cce
______________________________________________________________________________
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
Please see the 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.
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.
- SUSE runs two security mailing lists to which any interested party may
subscribe:
opensuse-security@opensuse.org
- General Linux and SUSE security discussion.
All SUSE security announcements are sent to this list.
To subscribe, send an e-mail to
.
opensuse-security-announce@opensuse.org
- SUSE's announce-only mailing list.
Only SUSE's security announcements are sent to this list.
To subscribe, send an e-mail to
.
==================================================================== SUSE's security contact is or .
The public key is listed below.
====================================================================