The kernel packages contain the Linux kernel, the core of any Linux operating system.
This update fixes the following security issue:
It was found that a deadlock could occur in the Out of Memory (OOM) killer. A process could trigger this deadlock by consuming a large amount of memory, and then causing request_module() to be called. A local, unprivileged user could use this flaw to cause a denial of service (excessive memory consumption). The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-4398 to this issue.
More information about these vulnerabilities can be found in the security advisory issued by Red Hat:
|Product:||Affected Version(s):||Risk Level:||Actions:|
|Avaya Aura® Application Enablement Services||5.x, 6.1 thru 6.3.2||Medium||Upgrade to 6.3.3 or later.|
|Avaya Aura® Application Server 5300:
||2.x, 3.0 without SP7||Medium||For 2.x upgrade to 3.0 and install Service Pack 7 or later.
For 3.0 install Service Pack 7 or later.
|Avaya IQ||4.x, 5.0 thru 5.2.5||Medium||Upgrade to 5.2.6 and install Patch 2 or later.|
|Avaya Aura® Communication Manager||5.2.x, 6.0 thru 6.3||Low||For 6.2 and earler install 6.3 and Kernel Service Pack 2 as detailed in PCN1922S.
For 6.3 install 6.3 Kernel Service Pack 2 as detailed in PCN1922S.
|Avaya Communication Server 1000:
||6.x, 7.5, 7.6 thru 7.6 SP4||Medium||For 7.5 and earlier upgrade to 7.6 and installed Service Pack 5 or later.
For 7.6 install Service Pack 5 or later.
|Avaya Aura® Conferencing||7.0, 7.2 without SP3||Low||For 7.0 upgrade to 7.2 and install Service Pack 3 or later.
For 7.2 install Service Pack 3 or later.
|Avaya Aura® Conferencing Standard Edition||6.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 7.0 or later.|
|Avaya IP Office Application Server||8.x||Medium||Upgrade to 9.0 or later.|
|Avaya Meeting Exchange||6.2 thru 6.2 SP1||Medium||Upgrade to 6.2 SP2 or later.|
|Avaya Aura® Messaging||6.0 thru 6.3.1||Low||Upgrade to 6.3.2 or later.|
|Avaya one-X® Client Enablement Services||6.1.x||Medium||Upgrade to 6.2 and install Service Pack 1 or later.|
|Avaya Aura® Presence Services||6.x||Low||Upgrade to Aura Presence Services 7.0 or later. Further information about this version, as well as the overall Aura 7.0 release, is available on support.avaya.com.|
|Avaya Proactive Contact||5.0, 5.1||Medium||Upgrade to 5.1.1 or later.|
|Avaya Aura® Session Manager||1.x, 5.x, 6.0 thru 6.2.x||Medium||Upgrade to 6.3.4 or later.|
|Avaya Aura® SIP Enablement Services||5.2.x||Low||See Mitigating Factors below. There are no current plans to resolve this issue.|
|Avaya Aura® System Manager||5.x, 6.0 thru 6.3.4||Medium||Upgarde to 6.3.5 or later.|
|Avaya Aura® System Platform||1.x, 6.0 thru 6.3.3||Low||Upgrade to 6.3.4 or later.|
|Avaya Aura® Communication Manager Utility Services||6.0 thru 6.3.2||Medium||For 6.1 and earlier upgrade to 6.3 and install Service Pack 126.96.36.199.20 or later.
For 6.2 install Service Pack 188.8.131.52.15 or later.
For 6.3 install Service Pack 184.108.40.206.20 or later.
|Avaya Voice Portal||5.x||Medium||See recommended actions and Mitigating Factors table below. This advisory will not be addressed as there will be no further releases. It is recommended to upgrade to Avaya Aura® Experience Portal.|
Recommended Actions for System Products:
Avaya strongly recommends following the 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 the System Product operating system or application should not be modified 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:
||This is a Low risk for Communication Manager, Conferencing, Messaging, Presence Services, System Platform and SIP Enablement Services as only privileged accounts may upload and run executables, so no additional capability would be gained.
This is a medium risk for the other products due to the potential for a local unprivileged user to cause a Denial of Service.
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.
|Avaya Aura® Application Enablement Services||Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the AES application.|
|CVLAN||Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the CVLAN application.|
|Avaya Aura® Experience Portal||Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the EP application.|
|Avaya Integrated Management Suite (IMS)||Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the IMS application.|
|Avaya Aura® Presence Services||Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the PS application.|
|Avaya Secure Access Link Gateway||Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the SAL Gateway application.|
|Avaya Voice Portal||Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the VP application.|
Recommended Actions for Software-Only Products:
In the event that the affected package is installed, Avaya recommends following the 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 - October 30, 2013 - Initial Statement issued.
V 2.0 - February 19, 2014 - Updated SMGR, CMUS and VP affected versions and actions.
V 3.0 - March 13, 2014 - Updated AS5300 and one-X CES affected versions and actions.
V 4.0 - May 16, 2014 - Updated Conferencing affected versions and actions.
V 5.0 - June 12, 2014 - Updated AES, CS1000, PC and SP affected versions and actions.
V 6.0 - February 17, 2015 - Updated CM and Messaging affected versions and actions.
V 7.0 - September 11, 2015 - Updated PS actions, IQ affected versions and actions.
V 8.0 - July 22, 2016 - Changed Meeting Exchange affected versions and actions, and 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 email@example.com.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
© 2013 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.