kernel security update (RHSA-2007-0488)

Original Release Date: July 30, 2007
Last Revised: February 25, 2009
Number: ASA-2007-287
Risk Level: Low
Advisory Version: 3.0
Advisory Status: Interim

1. Overview:

The Linux kernel manages the communication between software and hardware as well as the hardware resources of a computer running the Linux operating system.

Red Hat has issued an updated version of the kernel packages. Below is a list of the security issues fixed in the update as reported by Red Hat:

  • a flaw in the connection tracking support for SCTP that allowed a remote user to cause a denial of service by dereferencing a NULL pointer.
  • a flaw in the mount handling routine for 64-bit systems that allowed a local user to cause denial of service (crash).
  • a flaw in the IPv4 forwarding base that allowed a local user to cause an out-of-bounds access.
  • a flaw in the PPP over Ethernet implementation that allowed a local user to cause a denial of service (memory consumption) by creating a socket using connect and then releasing it before the PPPIOCGCHAN ioctl has been called.
  • a flaw in the fput ioctl handling of 32-bit applications running on 64-bit platforms that allowed a local user to cause a denial of service (panic).
  • a flaw in the NFS locking daemon that allowed a local user to cause denial of service (deadlock).
  • a flaw in the sysfs_readdir function that allowed a local user to cause a denial of service by dereferencing a NULL pointer.
  • a flaw in the core-dump handling that allowed a local user to create core dumps from unreadable binaries via PT_INTERP.
  • a flaw in the Bluetooth subsystem that allowed a local user to trigger an information leak.
  • The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2007-2876, CVE-2006-7203, CVE-2007-2172, CVE-2007-2525, CVE-2007-0773, CVE-2006-5158, CVE-2007-3104, CVE-2007-0958 and CVE-2007-1353 to these issues.

    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 3.1 and CM 4.x Low Upgrade to CM 5.0 or later.
    Avaya Messaging Storage Server MSS 3.x Low Upgrade to MSS 4.0 or later.
    Avaya Message Networking All Low See recommended actions below.  This issue will be addressed in accordance with Avaya's Product Security Vulnerability Response Policy
    Avaya CCS/SES SES 3.1.1 or newer Low Upgrade to SES 5.0 or later.
    Avaya AES AES 4.x Low Upgrade to AES 4.2 or later.

    Recommended Actions:
    For all system products which use vulnerable versions of the kernel, 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.

    4. Software-Only Products:

    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. The CVLAN application does not require the software described in this advisory.
    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. The IMS application does not require the software described in this advisory.

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

    5. 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.

    6. 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.

    7. Revision History:

    V 1.0 - July 30, 2007 - Initial Statement issued.
    V 2.0 - July 30, 2008 - Updated the affected versions for AES and changed the recommended actions for AES, CM and SES.
    V 3.0 - February 25, 2009 - Changed MSS recommended actions.

    Send information regarding any discovered security problems with Avaya products to either the contact noted in the product's documentation or securityalerts@avaya.com.

    © 2007 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.