The kernel packages contain the Linux kernel, the core of any Linux operating system.
This update fixes the following security issues:
* A flaw was found in the way the Xen hypervisor implementation handled instruction emulation during virtual machine exits. A malicious user-space process running in an SMP guest could trick the emulator into reading a different instruction than the one that caused the virtual machine to exit. An unprivileged guest user could trigger this flaw to crash the host. This only affects systems with both an AMD x86 processor and the AMD Virtualization (AMD-V) extensions enabled. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1780 to this issue.
* A flaw allowed the tc_fill_qdisc() function in the Linux kernel's packet scheduler API implementation to be called on built-in qdisc structures. A local, unprivileged user could use this flaw to trigger a NULL pointer dereference, resulting in a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-2525 to this issue.
* A flaw was found in the way space was allocated in the Linux kernel's Global File System 2 (GFS2) implementation. If the file system was almost full, and a local, unprivileged user made an fallocate() request, it could result in a denial of service. Note: Setting quotas to prevent users from using all available disk space would prevent exploitation of this flaw. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-2689 to this issue.
More information about these vulnerabilities can be found in the security advisories issued by Red Hat:
Product: | Affected Version(s): | Risk Level: | Actions: |
---|---|---|---|
Avaya Aura® Application Enablement Services | 5.2.x, 6.1, 6.1.1 | Low | Upgrade to Application Enablement Services 6.1.2 or later. |
Avaya Aura® Application Server 5300:
|
2.0 including PB1 through PB15 | Low | Upgrade to Application Server 5300 2.0 PB16 or later. |
Avaya Aura® Communication Manager | 5.2.x, 6.0.x, 6.2.x | Low | Upgrade to Communication Manager 6.3 or later. |
Avaya Communication Server 1000:
|
6.0, 7.0, 7.5 | Low | Upgrade to Communication Server 1000 7.6 or later. |
Avaya Aura® Conferencing Standard Edition | 6.0.x | Low | 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 7.0 or later. |
Avaya IQ | 5.2 thru 5.2.5 | Low | Upgrade to IQ 5.2.6 and install Patch 2 or later. |
Avaya Aura® Messaging | 6.0 through 6.2.x | Low | Upgrade to 6.3 or later. |
Avaya Aura® Presence Services | 6.0, 6.1, 6.1.1 | Low | Upgrade to Presence Services 6.1.2 or later. |
Avaya Aura® Session Manager | 1.1, 5.2, 6.0.x, 6.1 through 6.1.4 | Low | Upgrade to Session Manager 6.1.5 or later. |
Avaya Aura® System Manager | 5.2, 6.0.x, 6.1.x, 6.2.x | Low | Upgrade to System Manager 6.3 or later. |
Avaya Aura® System Platform | 1.1, 6.0 through 6.0.3.5.3 | Low | Upgrade to System Platform 6.0.3.0.3 and install patch 6.0.3.6.3 or later. |
Avaya Aura® Communication Manager Utility Services | 6.0, 6.1 | Low | Upgrade to Communication Manager Utility Services 6.2 or later. |
Avaya Voice Portal | 5.0.x, 5.1, 5.1.1 | Low | Upgrade to Avaya Linux for Voice Portal 5.1 SP2 and Voice Portal 5.1 SP2 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.
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-2011-1780 | This is no risk as products do not use an AMD processor. |
CVE-2011-2525 | This is a low risk due to exploitability being difficult and requiring non-standard direct local privileged user interaction. |
CVE-2011-2689 | This is a low risk as products do not use Global File System 2 by default. |
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.
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.
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.
V 1.0 - September 13, 2011 - Initial Statement issued.
V 2.0 - April 5, 2012 - Changed AES, AS5300, PS, SM, SP, CMUS and VP affected versions and actions.
V 3.0 - December 21, 2012 - Changed SMGR affected versions and actions.
V 4.0 - May 24, 2013 - Changed CM and CS1000 affected versions and actions.
V 5.0 - June 26, 2013 - Changed Conferencing SE actions.
V 6.0 - March 26, 2014 - Changed Messaging affected versions and actions.
V 7.0 - June 25, 2015 - Changed 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.