kernel security and bug fix update (RHSA-2009-0014)

Original Release Date: February 12, 2009
Last Revised: June 5, 2009
Number: ASA-2009-058
Risk Level: Low
Advisory Version: 4.0
Advisory Status: Interim

1. Overview:

The kernel packages contain the Linux kernel, the core of any Linux operating system.

This update addresses the following security issues:

* the sendmsg() function in the Linux kernel did not block during UNIX socket garbage collection. This could, potentially, lead to a local denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2008-5300 to this issue.

* when fput() was called to close a socket, the __scm_destroy() function in the Linux kernel could make indirect recursive calls to itself. This could, potentially, lead to a local denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2008-5029 to this issue.

* a deficiency was found in the Linux kernel virtual file system (VFS) implementation. This could allow a local, unprivileged user to make a series of file creations within deleted directories, possibly causing a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2008-3275 to this issue.

* a buffer underflow flaw was found in the Linux kernel IB700 SBC watchdog timer driver. This deficiency could lead to a possible information leak. By default, the "/dev/watchdog" device is accessible only to the root user. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2008-5702 to this issue.

* the hfs and hfsplus file systems code failed to properly handle corrupted data structures. This could, potentially, lead to a local denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2008-4933 and CVE-2008-5025 to these issues.

* a flaw was found in the hfsplus file system implementation. This could, potentially, lead to a local denial of service when write operations were performed. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2008-4934 to this issue.

More information about these vulnerabilities can be found in the security advisory issued by RedHat Linux:

2. Avaya System Products with kernel installed:

Product: Affected Version(s): Risk Level: Actions:
Avaya Communication Manager CM 5.1.x and earlier Low Upgrade to CM 5.2 or later.
Avaya Intuity AUDIX LX IALX 2.0, 2.0SP1, 2.0SP2 Low Will not be addressed as no further releases are planned.
Avaya Messaging Storage Server MSS 3.x, 4.0, 5.0 Low See recommended actions below.  This issue will be addressed in accordance with section five of Avaya's Product Security Vulnerability Response Policy
Avaya Message Networking MN 3.1 Low See recommended actions below.  This issue will be addressed in accordance with section five of Avaya's Product Security Vulnerability Response Policy
Avaya SIP Enablement Services SES 5.1 and earlier Low Upgrade to SES 5.2 or later.
Avaya Voice Portal VP 3.x, 4.x Low Upgrade to VP 5.0 or later
Avaya Meeting Exchange MX 5.0 SP2, 5.1 Low See recommended actions below.  This issue will be addressed in accordance with section five of Avaya's Product Security Vulnerability Response Policy
Avaya Proactive Contact PC 4.0, 4.1 Low Upgrade to PC 4.1.1 or later.
Avaya AES AES 4.2.1 and ealier Low Upgrade to AES 4.2.2 or later.

Recommended Actions:
For all vulnerable system products, Avaya recommends that customers restrict local and network access to the server. This restriction should be enforced through the use of physical security, firewalls, ACLs, VPNs, and other generally-accepted networking practices until such time as an update becomes available and can be installed.

3. Avaya Software-Only Products:

Avaya software-only products operate on general-purpose operating systems. Occasionally vulnerabilities may be discovered in the underlying operating system or applications that come with the operating system. These vulnerabilities often do not impact the software-only product directly but may threaten the integrity of the underlying platform.

In the case of this advisory Avaya software-only products are not affected by the vulnerability directly but the underlying Linux platform may be. Customers should determine on which Linux operating system the product was installed and then follow that vendor's guidance.

Product: Actions:
CVLAN Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the CVLAN application.
Avaya Integrated Management Suite (IMS) Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the IMS application.
Voice Portal Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the Voice Portal application.
AES 4.x Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the AES application.

Recommended Actions:
In the event that the affected package is installed, Avaya recommends that customers follow recommended actions supplied by RedHat Linux.

4. Additional Information:

Additional information may also be available via the Avaya support website and through your Avaya account representative. Please contact your Avaya product support representative, or dial 1-800-242-2121, with any questions.

5. Disclaimer:

ALL INFORMATION IS BELIEVED TO BE CORRECT AT THE TIME OF PUBLICATION AND IS PROVIDED "AS IS". AVAYA INC., ON BEHALF ITSELF AND ITS SUBSIDIARIES AND AFFILIATES (HEREINAFTER COLLECTIVELY REFERRED TO AS "AVAYA"), DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND FURTHERMORE, AVAYA MAKES NO REPRESENTATIONS OR WARRANTIES THAT THE STEPS RECOMMENDED WILL ELIMINATE SECURITY OR VIRUS THREATS TO CUSTOMERS' SYSTEMS. IN NO EVENT SHALL AVAYA BE LIABLE FOR ANY DAMAGES WHATSOEVER ARISING OUT OF OR IN CONNECTION WITH THE INFORMATION OR RECOMMENDED ACTIONS PROVIDED HEREIN, INCLUDING DIRECT, INDIRECT, INCIDENTAL, STATUTORY, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF AVAYA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

THE INFORMATION PROVIDED HERE DOES NOT AFFECT THE SUPPORT AGREEMENTS IN PLACE FOR AVAYA PRODUCTS. SUPPORT FOR AVAYA PRODUCTS CONTINUES TO BE EXECUTED AS PER EXISTING AGREEMENTS WITH AVAYA.

6. Revision History:

V 1.0 - February 12, 2009 - Initial Statement issued.
V 2.0 - May 12, 2009 - Changed CM and SES affected versions and actions, and changed VP actions.
V 3.0 - May 19, 2009 - Changed IALX actions.
V 4.0 - June 5, 2009 - Changed PC and AES affected verisions and actions.

Send information regarding any discovered security problems with Avaya products to either the contact noted in the product's documentation or [email protected].

© 2009 Avaya Inc. All Rights Reserved. All trademarks identified by the ® or ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.