The kernel packages contain the Linux kernel, the core of any Linux operating system.
A flaw was found in the way the Linux kernel's futex subsystem handled the requeuing of certain Priority Inheritance (PI) futexes. A local, unprivileged user could use this flaw to escalate their privileges on the system. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-3153 to this issue.
A flaw was found in the way the Linux kernel's floppy driver handled user space provided data in certain error code paths while processing FDRAWCMD IOCTL commands. A local user with write access to /dev/fdX could use this flaw to free (using the kfree() function) arbitrary kernel memory. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-1737 to this issue.
It was found that the Linux kernel's floppy driver leaked internal kernel memory addresses to user space during the processing of the FDRAWCMD IOCTL command. A local user with write access to /dev/fdX could use this flaw to obtain information about the kernel heap arrangement. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-1738 to this issue.
It was discovered that the proc_ns_follow_link() function did not properly return the LAST_BIND value in the last pathname component as is expected for procfs symbolic links, which could lead to excessive freeing of memory and consequent slab corruption. 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-0203 to this issue.
A flaw was found in the way the Linux kernel handled exceptions when user-space applications attempted to use the linkage stack. On IBM S/390 systems, 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-2039 to this issue.
An invalid pointer dereference flaw was found in the Marvell 8xxx Libertas WLAN (libertas) driver in the Linux kernel. A local user able to write to a file that is provided by the libertas driver and located on the debug file system (debugfs) could use this flaw to crash the system. Note: The debugfs file system must be mounted locally to exploit this issue. It is not mounted by default. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-6378 to this issue.
A denial of service flaw was discovered in the way the Linux kernel's SELinux implementation handled files with an empty SELinux security context. A local user who has the CAP_MAC_ADMIN capability could use this flaw to crash the system. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-1874 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 CMS||R17 thru R17 R3||Medium||Upgrade to R17 R4 or later.|
|Avaya Aura® Collaboration Environment||2.x, 3.0 including SP1||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||Low||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.
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:
||There is a Low risk as the Libertas WLAN driver is not installed or used by default.|
||This is a Low risk for Session Manager as no local unprivileged users are configured by default.
This is a Medium risk for other listed products due to the potential for an unprivileged user to crash the system.
|These are a Low risk as floppy drives are not configured or supported by default.|
||This is a Low risk as SELinux is not used by default.|
||There is no risk as IBM S/390 systems are not used or supported.|
||This is a Low risk for Session Manager as no local uprivileged users are configured.
This is a Medium risk for other listed products due to the potential for privilege escalation.
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® 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.
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 - July 8, 2014 - Initial Statement issued.
V 2.0 - February 25, 2015 - Updated CMS, CE and EP affected versions and actions.
V 3.0 - June 10, 2015 - Changed SM affected versions and actions.
V 4.0 - August 26, 2015 - Changed one-X CES affected versions and actions.
V 5.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 email@example.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.