-----BEGIN PGP SIGNED MESSAGE-----
______________________________________________________________________________
SUSE Security Announcement
Package: kernel
Announcement ID: SUSE-SA:2007:021
Date: Fri, 16 Mar 2007 13:00:00 +0000
Affected Products: SUSE LINUX 10.0
openSUSE 10.2
Vulnerability Type: remote denial of service
Severity (1-10): 7
SUSE Default Package: yes
Cross-References: CVE-2006-2936, CVE-2006-5749, CVE-2006-5751
CVE-2006-5753, CVE-2006-6106, CVE-2007-0006
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:
none
6) Authenticity Verification and Additional Information
______________________________________________________________________________
1) Problem Description and Brief Discussion
The Linux kernel was updated to fix the security problems listed below.
This advisory is for the bugs already announced for SUSE Linux
Enterprise 10 and SUSE Linux 10.1 in SUSE-SA:2007:018.
The packages associated with this update were already released 1
week ago.
Please note that bootloader handling in openSUSE 10.2 has changed and
now creates new entries for updated kernels and make those the default.
We also had reports of the update breaking the bootloader
configuration, and apologize for the inconveniences caused. We are
investigating those problems and hope to release an update to fix
the bootloader handling code.
If you are manually adapting /boot/grub/menu.lst, please review this
file after the update.
- 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-5751: An integer overflow in the networking bridge ioctl
starting with Kernel 2.6.7 could be used by local attackers to
overflow kernel memory buffers and potentially escalate privileges.
- 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-0006: The key serial number collision avoidance code in
the key_alloc_serial function allows local users to cause a denial
of service (crash) via vectors that trigger a null dereference.
- CVE-2007-0772: A remote denial of service problem on NFSv2 mounts
with ACL enabled was fixed.
Furthermore, openSUSE 10.2 catches up to the mainline kernel, version
2.6.18.8, and contains a large number of additional fixes for non
security bugs.
2) Solution or Work-Around
There is no known workaround, please install the update packages.
3) Special Instructions and Notes
Please reboot the system after installing the updated packages.
Review the /boot/grub/menu.lst configuration file if you manually changed it.
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:
openSUSE 10.2:
e82b0a67a4b0bbb0971bb969c8d9eb60
60c6ce6820d3839ce9fbe2eb4bab356c
da0bf89980c93e0a475e37fa200e28b0
4bf99d7816ba585f0ed5593dc6fbb740
13bc3b2be8b6fd08ae1589f9cfd67be7
08da4cbf6da45be1c0459580cb44749c
112d3fcfbea319940262c0a306da85be
3096d2eeb901ee592a06d68ca91982a9
9429c6f7042ebd28831298058467044a
d2cd5d41af38cf5489b9b7636546ce39
1c01b355d52b01f8cacbdfb06af0c171
d402122d25eab3352c194a96a249cc20
8798fe7a1d4ce2b2029bf4ee957efe08
dd3d8c1869f08c6c9d7821fd122d7b99
d1b16cbbc1445c7564bcdc8f009760a6
ba2fbb5381abcfac608f6dfd9ccca71c
bda4e19bab973eace8b245b82a976610
3998dbfbad2955c876d3c6918e30775b
20710daf7c1e1c7560387605e679e9ef
02dcd27ebad0f8b4eeaba2567ef79352
caea9f949b562b7fbe6cc1e5f7da4a4c
SUSE LINUX 10.0:
70a42a7f7742d66894bee17b3f388a5d
16b76176c41ecc466f9fb46cdd230489
062a8b04cb89e3989d305bef87dc0757
faf638689b69c1e80569bc46dbfe088b
6049934f03e60aca2bc5d54012c0407d
6c1ac1600ee0f27e7464e0407405f9aa
752faf01a1b41613c91f785e72895a55
e5fe6448fddbc8fcefd8a90b36888db9
e38e9ba4c63044e5bfbb285911c898a5
0944ef9eb3fe1634bf21121bf1f51fdc
9e6bd3a6f743926b9270872fefb9b915
9d49e4767426613e38573037776f26b0
8e5f25c2e2b85129f91c22c6868f0003
a38b42695a1f0700ac1ed8a71c79520c
Power PC Platform:
openSUSE 10.2:
56d9d481c3c62f9627f8fdb5b3df782d
109afa91f06beb989faa4ce3b5181ffa
1ce2d7597556be60d09b3cea3639af8a
84bd64a7f8d3de26f13536635983be23
56e7429616a92898cbf83ee796ae45f7
f79c0143fbf4ffd0cf14fa616968da58
97ab79266d28d0b05c7fe715e054bce1
SUSE LINUX 10.0:
419939cc75cdf648342e2de9bda2c0e8
5147690fdc8e20d2456d9a2ad9566c15
29982397729967c8237643d59f0a300b
6cf3159d8cef06756309a58f3a007e29
d16442f15524102ab709419e8a56f6a7
x86-64 Platform:
openSUSE 10.2:
c3841ced488b344daa86646138e1a050
a35ed0949cc2fe69362069398621788d
c884bd668d92648dddc440c931b44399
0aed77eee5442d9315f3d53c2da9f6f3
a37c3f4a169d9061af48d1430c04d05f
0c2f6be06580c9ca0426243c73e3144e
74d9189894b2ca61f495dc90023b279a
b0880efb1ff8ab29ea0ed752f692985d
8df8f3c772f884481a122abbe264c45d
SUSE LINUX 10.0:
9bb317c036977483961d7d4ab2c3a123
a57e4271abb5b607dcf24ccb7c75d3ea
7c0fd656bf08fa0a1dd9bce20ced8b2a
a5f66edd202201ffb96eadeb03a7213c
f195f6ebb24ef1b6ebf6859efe4e9658
9b23bb08beccedecc5ce35e1b099ca2f
a34f4798ccf607f3e6e8c1db4ce6ab1c
3aa25da4d80b5687b0dd112ccbb980f2
Sources:
openSUSE 10.2:
a6bb16929d315cf146675e75b3e14e97
d18038925c29a061a23fdbd3c410d362
e579ee0834be9cc99f0f181f4eefc722
099041a3de7a607b414c5690dc870117
7f7c7fd1543e01c24c1b9e7f71fb73a1
10d98ce9df7766e3a2268f103bea42d9
058b58f8be113977a91e94ab94bf0182
210b549a27e3eca6d7174ad1c3e4c858
SUSE LINUX 10.0:
e7669014790db2d2b9022d08307d7fba
a56233e08afeb0c3e7a7d47c4614fcc2
6b84ee8f314841da371d89efe4406e47
28a33e95d59a0fbfa8d7ec10d8bb7d43
f6e51f0333e0b8a571f6e7e070ac577d
fb5e7d691e697ae608e9964966060cdc
0bb6955fcaf7079ec5dc84d0242d518a
e4f1f529be352d96e39efd832bb1bd2b
44acc7bf9de3e6404876c72a264448d2
80a8dd4f5c4535c6f6cfc40b4d17591a
1b20f3e5ee1bf0b081a50f26f811b47e
______________________________________________________________________________
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
none
______________________________________________________________________________
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.
====================================================================
