kernel security, bug fix, and enhancement update (RHSA-2014-0981)

Original Release Date: August 8, 2014
Last Revised: October 15, 2015
Number: ASA-2014-312
Risk Level: Medium
Advisory Version: 4.0
Advisory Status: Final

1. Overview:

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

A use-after-free flaw was found in the way the ping_init_sock() function of the Linux kernel handled the group_info reference counter. A local, unprivileged user could use this flaw to crash the system or, potentially, escalate their privileges on the system. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-2851 to this issue.

A NULL pointer dereference flaw was found in the way the futex_wait_requeue_pi() function of the Linux kernel's futex subsystem handled the requeuing of certain Priority Inheritance (PI) futexes. A local, unprivileged user could use this flaw to crash the system. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-6647 to this issue.

A NULL pointer dereference flaw was found in the rds_ib_laddr_check() function in the Linux kernel's implementation of Reliable Datagram Sockets (RDS). A local, unprivileged user could use this flaw to crash the system. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-7339 to this issue.

It was found that a remote attacker could use a race condition flaw in the ath_tx_aggr_sleep() function to crash the system by creating large network traffic on the system's Atheros 9k wireless network adapter. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-2672 to this issue.

A NULL pointer dereference flaw was found in the rds_iw_laddr_check() function in the Linux kernel's implementation of Reliable Datagram Sockets (RDS). A local, unprivileged user could use this flaw to crash the system. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-2678 to this issue.

A race condition flaw was found in the way the Linux kernel's mac80211 subsystem implementation handled synchronization between TX and STA wake-up code paths. A remote attacker could use this flaw to crash the system. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-2706 to this issue.

An out-of-bounds memory access flaw was found in the Netlink Attribute extension of the Berkeley Packet Filter (BPF) interpreter functionality in the Linux kernel's networking implementation. A local, unprivileged user could use this flaw to crash the system or leak kernel memory to user space via a specially crafted socket filter. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2014-3144 and CVE-2014-3145 to these issues.

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 RHEL6 with affected packages installed:

Product: Affected Version(s): Risk Level: Actions:
Avaya CMS R17 thru R17 R3 Medium Upgrade to R17 R4 or later.
Avaya Aura® Collaboration Environment 2.x, 3.x Medium Upgrade to 3.0 SP2 or later.
Avaya Aura® Experience Portal 6.0 thru 6.0.3, 7.0 thru 7.0.1 Medium For 6.0, upgrade to 6.0.3 and Avaya Linux for 6.0.3 and install Security Updates for 6.0.3.
For 6.0.3, install Security Updates for 6.0.3.
For 7.0, install Security Updates for 7.0.
For 7.0.1, install Security Updates for 7.0.1.
Avaya IP Office Server Edition 8.1 thru 9.1.3 Medium Upgrade to 9.1.4 or later.
Avaya IP Office Application Server 9.0 thru 9.1.3 Medium Upgrade to 9.1.4 or later.
Avaya one-X® Client Enablement Services 6.2 thru 6.2.3 Medium Upgrade to 6.2.4 or later.
Avaya Aura® Session Manager 6.3 thru 6.3.9 Medium Upgrade to 6.3.10 or later.

Recommended Actions for System Products:
Avaya strongly recommends following 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.

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-2014-2851
This is a Medium risk due to the potential for privilege escalation, or an unprivileged user to crash the system.
CVE-2012-6647
CVE-2014-3144
CVE-2014-3145
These are a Medium risk due to the potential for an unprivileged user to crash the system.
CVE-2013-7339
CVE-2014-2678
These are a Low risk as the RDS protocol is not used or supported by default.
CVE-2014-2672
CVE-2014-2706
These are a Low risk as the affected subsystems are not used or supported by default.

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® Experience Portal Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the EP application.

Recommended Actions for Software-Only Products:
In the event that the affected package is installed, Avaya recommends following 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 8, 2014 - Initial Statement issued.
V 2.0 - February 26, 2015 - Updated CMS, EP and SM affected versions and actions.
V 3.0 - August 27, 2015 - Updated one-X CES affected versions and actions.
V 4.0 - October 15, 2015 - Changed IPOSE and IPOAS affected versions and actions, and set advisory status to final.

Avaya customers or Business Partners should report any security issues found with Avaya products via the standard support process.
Independent security researchers can contact Avaya at securityalerts@avaya.com.

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

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