-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: kernel-bigsmp
Announcement ID: SUSE-SA:2007:018
Date: Tue, 27 Feb 2007 14:00:00 +0000
Affected Products: SUSE LINUX 10.1
SUSE SLED 10
SUSE SLE 10 DEBUGINFO
SUSE SLES 10
Vulnerability Type: remote denial of service
Severity (1-10): 7
SUSE Default Package: yes
Cross-References: CVE-2006-2936, CVE-2006-4814, CVE-2006-5749
CVE-2006-5753, CVE-2006-6106, CVE-2007-0772
Content of This Advisory:
1) Security Vulnerability Resolved:
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
A kernel update has been released to fix the following security problems:
- CVE-2006-2936: The ftdi_sio driver allowed local users to cause a denial
of service (memory consumption) by writing more data to
the serial port than the hardware can handle, which causes
the data to be queued. This requires this driver to be
loaded, which only happens if such a device is plugged
in.
- CVE-2006-4814: A deadlock in mincore that could be caused by local
attackers was fixed.
- CVE-2006-6106: Multiple buffer overflows in the cmtp_recv_interopmsg
function in the Bluetooth driver
(net/bluetooth/cmtp/capi.c) in the Linux kernel allowed
remote attackers to cause a denial of service (crash) and
possibly execute arbitrary code via CAPI messages with a
large value for the length of the (1) manu (manufacturer)
or (2) serial (serial number) field.
- CVE-2006-5749: The isdn_ppp_ccp_reset_alloc_state function in
drivers/isdn/isdn_ppp.c in the Linux kernel does not
call the init_timer function for the ISDN PPP CCP
reset state timer, which has unknown attack vectors and results in a system crash.
- CVE-2006-5753: Unspecified vulnerability in the listxattr system call in
Linux kernel, when a "bad inode" is present, allows local
users to cause a denial of service (data corruption)
and possibly gain privileges.
- CVE-2007-0772: A remote denial of service problem on NFSv2 mounts with
ACL enabled was fixed.
and various non security bugs.
This update only covers SUSE Linux Enterprise 10 and SUSE Linux 10.1. The above
listed problems also affect other kernels, for which updates will be published.
2) Solution or Work-Around
There is no known workaround, please install the update packages.
3) Special Instructions and Notes
None.
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.
x86 Platform:
SUSE LINUX 10.1:
e8b387eecd54b875c1071fc924f4f2b4
001254c312faec605b5eaf0f5682a280
6eaecfb75cfab350ff1f4b965d08948b
46ba9fd7be425f3db58daac13ddcfe1b
c9fb15081967d858ad7b29ead84a1259
47dd412f9add6ec37697347266724dab
05fdd39d25567fdc05b70d9176d2542c
1a068a49ecd18a073301216a5952a8a7
6ff11d2cc96dc3294189877419cf86e4
a5527c57faded347005b60c9681be126
54266b9c20d734c8aad15003dba12eb1
9804a7f76037c8db855b77141252aeec
a363de03cb38de046cf5d6a76f13a1cb
3ef0734f0ae0bbcb723a7b78701fa42a
e5febb721512dad8f25bfe9343154b99
Power PC Platform:
SUSE LINUX 10.1:
bffed3ad3f3510a833985fe5c7f943c1
44050e412ee8ac6bfe124bcb1804c3fc
6c74ba711d9c11436b20b932723aff6b
8f491b0fbf372b38883013cb336526e0
c7fc5634e2e74f5d263ab317c494ce2c
ca22718fdbb03666b86200fa4bf8827d
8eed776dd3ad2222675925cdcc489a8c
16fc2022787b0c6c4e683b851375ce7a
010256c84bd145fa9ffacb313cb08934
09b5b91d25edb12c5ca941257fd51c5a
x86-64 Platform:
SUSE LINUX 10.1:
8d959b18857fc50c549939a1be7724ba
54fae8532c291f373f6f23d08f3b20bc
a9d9c3e6213f06230fe7cbb2e2a1a16a
23c385bb7f183d938faf5792cafa6098
acfb4766596756d2402711056caa4c8d
c7caaf1a1d2bd2691215a74541cb63de
b91eb4928f6b137344bb8276f480d8f9
211671c57618d29c2cb684e209375b69
e57c6fc9dfb9716c732ee7414b3f4d34
8641961daf3b7bbafb140a63c8004d65
d956cb94731fe3aa3055c08248784921
290ccf945f68f274eb1d346ad54f22ad
Sources:
SUSE LINUX 10.1:
42819b35570ec966f4899bf074494ba1
9efb9aca7660d69d021dd6cf591e279a
6f3302e4c5ba828eab6a01713fff1901
72e5ee51ff22fac8d4a56034dc5726e0
95a5532d49a13f2f4d080618eafa5abb
b67adf4fdf41dd4afc324758eb81b643
5dfce38d6737c14879439cca7c615ec0
eda39963f17d3334ba75abe2cd41e71a
87d2443ec4e18d188963e5d5ac8bb41c
7544736387458c7eadfae00f70cd7642
c9db84dd6382927b79a5f6594e84895f
b60d4f1da62f64f5e982a64bd7bdcd5b
eb6c84b6338d297ff625fd9eb220e0d7
58a2d662fe0906295b90d6bef6d4e760
18bb0bd55194f2e50b60e9998eeaef0b
64b5b42d879d4669c9f42eb576aa63fe
6fe2ea0869a47c552dc66378555adf99
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
SUSE SLED 10 for AMD64 and Intel EM64T
http://support.novell.com/techcenter/psdb/07f0172bd1d7fcba7b4b05eb27a13a69.html
SUSE SLE 10 DEBUGINFO for IBM zSeries 64bit
http://support.novell.com/techcenter/psdb/6b9ee4fae636f4681a5d171bade9e2b6.html
SUSE SLE 10 DEBUGINFO for IBM POWER
http://support.novell.com/techcenter/psdb/1fc9802c03b4f29a29158627871433df.html
SUSE SLE 10 DEBUGINFO for IPF
http://support.novell.com/techcenter/psdb/84b59ac1863082bf630b430a98ccb5ca.html
SUSE SLES 10
http://support.novell.com/techcenter/psdb/07f0172bd1d7fcba7b4b05eb27a13a69.html
http://support.novell.com/techcenter/psdb/6b9ee4fae636f4681a5d171bade9e2b6.html
http://support.novell.com/techcenter/psdb/1fc9802c03b4f29a29158627871433df.html
http://support.novell.com/techcenter/psdb/84b59ac1863082bf630b430a98ccb5ca.html
http://support.novell.com/techcenter/psdb/7a120195d0f5166ddeb25518b0ee41d0.html
SUSE SLE 10 DEBUGINFO
http://support.novell.com/techcenter/psdb/07f0172bd1d7fcba7b4b05eb27a13a69.html
http://support.novell.com/techcenter/psdb/1fc9802c03b4f29a29158627871433df.html
http://support.novell.com/techcenter/psdb/84b59ac1863082bf630b430a98ccb5ca.html
http://support.novell.com/techcenter/psdb/7a120195d0f5166ddeb25518b0ee41d0.html
SUSE SLED 10
http://support.novell.com/techcenter/psdb/07f0172bd1d7fcba7b4b05eb27a13a69.html
http://support.novell.com/techcenter/psdb/7a120195d0f5166ddeb25518b0ee41d0.html
SUSE SLED 10 for x86
http://support.novell.com/techcenter/psdb/7a120195d0f5166ddeb25518b0ee41d0.html
______________________________________________________________________________
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.
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) Using the internal gpg signatures of the rpm package
2) MD5 checksums as provided in this announcement
1) 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.
2) If you need an alternative means of verification, use the md5sum
command to verify the authenticity of the packages. 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
SUSE security announcement. Because the announcement containing the
checksums is cryptographically signed (by security@suse.de), the
checksums show proof of the authenticity of the package if the
signature of the announcement is valid. Note that the md5 sums
published in the SUSE Security Announcements are valid for the
respective packages only. Newer versions of these packages cannot be
verified.
- 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
.
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 e-mail to
.
==================================================================== SUSE's security contact is or .
The public key is listed below.
====================================================================
