-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: kernel
Announcement ID: SUSE-SA:2009:008
Date: Thu, 29 Jan 2009 13:00:00 +0000
Affected Products: openSUSE 10.3
openSUSE 11.0
SLE SDK 10 SP2
SUSE Linux Enterprise Desktop 10 SP2
SUSE Linux Enterprise 10 SP2 DEBUGINFO
SUSE Linux Enterprise Server 10 SP2
Vulnerability Type: local privilege escalation
Severity (1-10): 7
SUSE Default Package: yes
Cross-References: CVE-2008-4933, CVE-2008-5025, CVE-2008-5029
CVE-2008-5079, CVE-2008-5182
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:
See SUSE Security Summary Report.
6) Authenticity Verification and Additional Information
______________________________________________________________________________
1) Problem Description and Brief Discussion
The SUSE Linux Enterprise 10 Service Pack 2 kernel was updated to
version 2.6.16.60-0.34 to fix some security issues and various bugs.
The following security problems have been fixed:
CVE-2008-5079: net/atm/svc.c in the ATM subsystem allowed local users to cause a denial of service (kernel infinite loop) by making two calls
to svc_listen for the same socket, and then reading a /proc/net/atm/
*vc file, related to corruption of the vcc table.
CVE-2008-5029: The __scm_destroy function in net/core/scm.c makes
indirect recursive calls to itself through calls to the fput function,
which allows local users to cause a denial of service (panic) via
vectors related to sending an SCM_RIGHTS message through a UNIX domain
socket and closing file descriptors.
CVE-2008-4933: Buffer overflow in the hfsplus_find_cat function in
fs/hfsplus/catalog.c allowed attackers to cause a denial of service
(memory corruption or system crash) via an hfsplus filesystem
image with an invalid catalog namelength field, related to the
hfsplus_cat_build_key_uni function.
CVE-2008-5025: Stack-based buffer overflow in the hfs_cat_find_brec
function in fs/hfs/catalog.c allowed attackers to cause a denial of
service (memory corruption or system crash) via an hfs filesystem
image with an invalid catalog namelength field, a related issue to
CVE-2008-4933.
CVE-2008-5182: The inotify functionality might allow local users to
gain privileges via unknown vectors related to race conditions in
inotify watch removal and umount.
A lot of other bugs were fixed, a detailed list can be found in the
RPM changelog.
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 10 SP2 DEBUGINFO for IBM POWER
https://login.microfocus.com/nidp/app/login;keywords=315c54bd455583ce56f6bcbe19c768f9
SUSE Linux Enterprise 10 SP2 DEBUGINFO for IPF
https://login.microfocus.com/nidp/app/login;keywords=a91d4196357d841dd0ee16be55b3c171
SUSE Linux Enterprise 10 SP2 DEBUGINFO for IBM zSeries 64bit
https://login.microfocus.com/nidp/app/login;keywords=25b427c3c9c9b792a1e2c6f6c13f893d
SUSE Linux Enterprise Desktop 10 SP2 for AMD64 and Intel EM64T
https://login.microfocus.com/nidp/app/login;keywords=a12607704b9e51847bb7b81ca6d58c3b
SUSE Linux Enterprise Server 10 SP2
https://login.microfocus.com/nidp/app/login;keywords=315c54bd455583ce56f6bcbe19c768f9
https://login.microfocus.com/nidp/app/login;keywords=a91d4196357d841dd0ee16be55b3c171
https://login.microfocus.com/nidp/app/login;keywords=25b427c3c9c9b792a1e2c6f6c13f893d
https://login.microfocus.com/nidp/app/login;keywords=a12607704b9e51847bb7b81ca6d58c3b
https://login.microfocus.com/nidp/app/login;keywords=14d206b16e1f6db4bc74003f9d937ed2
SLE SDK 10 SP2
https://login.microfocus.com/nidp/app/login;keywords=315c54bd455583ce56f6bcbe19c768f9
https://login.microfocus.com/nidp/app/login;keywords=a91d4196357d841dd0ee16be55b3c171
https://login.microfocus.com/nidp/app/login;keywords=a12607704b9e51847bb7b81ca6d58c3b
https://login.microfocus.com/nidp/app/login;keywords=14d206b16e1f6db4bc74003f9d937ed2
SUSE Linux Enterprise 10 SP2 DEBUGINFO
https://login.microfocus.com/nidp/app/login;keywords=315c54bd455583ce56f6bcbe19c768f9
https://login.microfocus.com/nidp/app/login;keywords=a91d4196357d841dd0ee16be55b3c171
https://login.microfocus.com/nidp/app/login;keywords=a12607704b9e51847bb7b81ca6d58c3b
https://login.microfocus.com/nidp/app/login;keywords=14d206b16e1f6db4bc74003f9d937ed2
SUSE Linux Enterprise Desktop 10 SP2
https://login.microfocus.com/nidp/app/login;keywords=a12607704b9e51847bb7b81ca6d58c3b
https://login.microfocus.com/nidp/app/login;keywords=14d206b16e1f6db4bc74003f9d937ed2
SUSE Linux Enterprise Desktop 10 SP2 for x86
https://login.microfocus.com/nidp/app/login;keywords=14d206b16e1f6db4bc74003f9d937ed2
______________________________________________________________________________
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.
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.
====================================================================
