kernel security and bug fix update (RHSA-2011-0927)

Original Release Date: August 23, 2011
Last Revised: July 2, 2015
Number: ASA-2011-238
Risk Level: Medium
Advisory Version: 8.0
Advisory Status: Final

1. Overview:

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

This update fixes the following security issues:

* An integer overflow flaw in ib_uverbs_poll_cq() could allow a local, unprivileged user to cause a denial of service or escalate their privileges. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-4649 to this issue.

* A race condition in the way new InfiniBand connections were set up could allow a remote user to cause a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-0695 to this issue.

* A flaw in the Stream Control Transmission Protocol (SCTP) implementation could allow a remote attacker to cause a denial of service if the sysctl "net.sctp.addip_enable" variable was turned on (it is off by default). The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1573 to this issue.

* Flaws in the AGPGART driver implementation when handling certain IOCTL commands could allow a local, unprivileged user to cause a denial of service or escalate their privileges. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2011-1745 and CVE-2011-2022 to these issues.

* An integer overflow flaw in agp_allocate_memory() could allow a local, unprivileged user to cause a denial of service or escalate their privileges. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1746 to this issue.

* A flaw allowed napi_reuse_skb() to be called on VLAN (virtual LAN) packets. An attacker on the local network could trigger this flaw by sending specially-crafted packets to a target system, possibly causing a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1576 to this issue.

* An integer signedness error in next_pidmap() could allow a local, unprivileged user to cause a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1593 to this issue.

* A flaw in the way the Xen hypervisor implementation handled CPUID instruction emulation during virtual machine exits could allow an unprivileged guest user to crash a guest. This only affects systems that have an Intel x86 processor with the Intel VT-x extension enabled. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1936 to this issue.

* A flaw in inet_diag_bc_audit() could allow a local, unprivileged user to cause a denial of service (infinite loop). The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-2213 to this issue.

* A missing initialization flaw in the XFS file system implementation could lead to an information leak. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-0711 to this issue.

* A flaw in ib_uverbs_poll_cq() could allow a local, unprivileged user to cause an information leak. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1044 to this issue.

* A missing validation check was found in the signals implementation. A local, unprivileged user could use this flaw to send signals via the sigqueueinfo system call, with the si_code set to SI_TKILL and with spoofed process and user IDs, to other processes. Note: This flaw does not allow existing permission checks to be bypassed; signals can only be sent if your privileges allow you to already do so. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1182 to this issue.

* A heap overflow flaw in the EFI GUID Partition Table (GPT) implementation could allow a local attacker to cause a denial of service by mounting a disk containing specially-crafted partition tables. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1776 to this issue.

* Structure padding in two structures in the Bluetooth implementation was not initialized properly before being copied to user-space, possibly allowing local, unprivileged users to leak kernel stack memory to user-space. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-2492 to this issue.

More information about these vulnerabilities can be found in the security advisory issued by Red Hat:

2. Avaya System Products using a modified version of RHEL5 with affected components/packages installed:

Product: Affected Version(s): Risk Level: Actions:
Avaya Aura® Application Enablement Services 5.2, 5.2.1, 5.2.2, 5.2.3, 6.1, 6.1.1 Medium

For Application Enablement Services 5.2 before 5.2.4, upgrade to 5.2.4 or later.
For Application Enablement Services 6.1 before 6.1.2, upgrade to 6.1.2 or later.

Avaya Aura® Application Server 5300:
  • SIP Core
2.0 Medium Upgrade to 2.0 PB16 or later.
Avaya Aura® Communication Manager 5.2.x, 6.0.x Low For 5.2.1, install Kernel Service Pack 5 or later.
For 6.0.x, upgrade to 6.2 or later.
Avaya Communication Server 1000:
  • CS1000E
  • CS1000M
  • CS1000E/CS1000M Signaling Server
6.0, 7.0, 7.5 Low See recommended actions and Mitigating Factors table below. This advisory will not be addressed as no further releases are planned.
Avaya Aura® Conferencing Standard Edition 6.0.x Medium See recommended actions and Mitigating Factors table below. This advisory will not be addressed as no further releases are planned. It is recommended that customers migrate to one of Avaya's conferencing solutions including Aura® Conferencing 8.0 or later.
Avaya IP Office Application Server 6.x, 7.0 Medium Upgrade to 8.0 or later.
Avaya IQ 5.2 thru 5.2.5 Medium Upgrade to 5.2.6 and install Patch 2 or later.
Avaya Aura® Messaging 6.0.x, 6.1.x Low Upgrade to 6.2 or later.
Avaya Aura® Presence Services 6.0, 6.1, 6.1.1 Medium Upgrade to 6.1.2 or later.
Avaya Aura® Session Manager 1.1.x, 5.2.x, 6.0 thru 6.1.5 Medium Upgrade to 6.1.6 or later.
Avaya Aura® System Manager 5.2.x, 6.0.x, 6.1 thru 6.1.4 Medium Upgrade to 6.1.5 or later.
Avaya Aura® System Platform 1.1, 6.0.x Medium Upgrade to 6.2 or later.
Avaya Aura® Communication Manager Utility Services 6.0, 6.1 Low Upgrade to 6.2 or later.

Recommended Actions for System Products:
Avaya strongly recommends that customers follow networking and security best practices by implementing firewalls, ACLs, physical security or other appropriate access restrictions. Though Avaya believes such restrictions should always be in place, risk to Avaya products and the surrounding network from this potential vulnerability may be mitigated by ensuring these practices are implemented until such time as an Avaya provided product update or the recommended Avaya action is applied. Further restrictions as deemed necessary based on the customer's security policies may be required during this interim period, but customers should not modify the System Product operating system or application unless the change is approved by Avaya. Making changes that are not approved may void the Avaya product service contract.

Mitigating Factors:

When determining risk, Avaya takes into account many factors as outlined by Avaya's Security Vulnerability Classification Policy. The following table describes factors that mitigate the risk of specific vulnerabilities for affected Avaya products:

Vulnerability Mitigating Factors
CVE-2010-4649
CVE-2011-0695
CVE-2011-0711
CVE-2011-1044
CVE-2011-1182
CVE-2011-1573
CVE-2011-1576
CVE-2011-1593
CVE-2011-1745
CVE-2011-1746
CVE-2011-1776
CVE-2011-1936
CVE-2011-2022
CVE-2011-2213
CVE-2011-2492
These are rated Low Risk for Communication Manager, Messaging and Utility Services since high-level (root) permissions are required to exploit these vulnerabilities.
These are rated Low Risk for Communication Server 1000 since these vulnerabilities can only be exploited by a local authenticated user.
These are rated Medium Risk for all other products since they can cause a denial of service or escalate user's privileges.

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:
Avaya Aura® Application Enablement Services 4.x/5.x Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the AES application.
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.
Avaya Aura® Presence Services Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the PS application.
Avaya Aura® System Manager 1.0 Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the SMGR 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.

Recommended Actions for Software-Only Products:
In the event that the affected package is installed, Avaya recommends that customers follow recommended actions supplied by Red Hat regarding their Enterprise 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 - August 23, 2011 - Initial Statement issued.
V 2.0 - March 5, 2012 - Updated SM, AS5300, IP Office Application Server, PS, US and VP Actions.
V 3.0 - April 16, 2012 - Updated AES, CM, SP and SM actions.
V 4.0 - May 4, 2012 - Updated AES actions.
V 5.0 - September 19, 2012 - Updated AES and CM actions.
V 6.0 - December 7, 2012 - Updated SM actions; SP affected versions.
V 7.0 - April 1, 2015 - Updated actions for Conferencing SE, CS1K and Messaging.
V 8.0 - July 2, 2015 - Updated IQ affected versions and actions, and set advisory status to final.

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

Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.

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