The kernel packages contain the Linux kernel, the core of any Linux operating system.
This update fixes the following security issues:
* A buffer overflow flaw was found in the ecryptfs_uid_hash() function in the Linux kernel eCryptfs implementation. On systems that have the eCryptfs netlink transport (Red Hat Enterprise Linux 5 does) or where the "/dev/ecryptfs" file has world writable permissions (which it does not, by default, on Red Hat Enterprise Linux 5), a local, unprivileged user could use this flaw to cause a denial of service or possibly escalate their privileges. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-2492 to this issue.
* A miscalculation of the size of the free space of the initial directory entry in a directory leaf block was found in the Linux kernel Global File System 2 (GFS2) implementation. A local, unprivileged user with write access to a GFS2-mounted file system could perform a rename operation on that file system to trigger a NULL pointer dereference, possibly resulting in a denial of service or privilege escalation. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-2798 to this issue.
* A flaw was found in the Xen hypervisor implementation when running a system that has an Intel CPU without Extended Page Tables (EPT) support. While attempting to dump information about a crashing fully-virtualized guest, the flaw could cause the hypervisor to crash the host as well. A user with permissions to configure a fully-virtualized guest system could use this flaw to crash the host. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-2938 to this issue.
* Information leak flaws were found in the Linux kernel's Traffic Control Unit implementation. A local attacker could use these flaws to cause the kernel to leak kernel memory to user-space, possibly leading to the disclosure of sensitive information. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-2942 to this issue.
* A flaw was found in the Linux kernel's XFS file system implementation. The file handle lookup could return an invalid inode as valid. If an XFS file system was mounted via NFS (Network File System), a local attacker could access stale data or overwrite existing data that reused the inodes. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-2943 to this issue.
* An integer overflow flaw was found in the extent range checking code in the Linux kernel's ext4 file system implementation. A local, unprivileged user with write access to an ext4-mounted file system could trigger this flaw by writing to a file at a very large file offset, resulting in a local denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-3015 to this issue.
* An information leak flaw was found in the Linux kernel's USB implementation. Certain USB errors could result in an uninitialized kernel buffer being sent to user-space. An attacker with physical access to a target system could use this flaw to cause an information leak. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-1083 to this issue.
More information about these vulnerabilities can be found in the security advisory issued by RedHat Linux:
| Product: | Affected Version(s): | Risk Level: | Actions: |
|---|---|---|---|
| Avaya Aura® Application Enablement Services | 5.x | Low | Upgrade to AES 5.2.3 or later. |
| Avaya Aura® Communication Manager | 5.2, 6.0.x | Low | For CM 5.2, upgrade to CM 5.2.1 and install Kernel Service Pack (KSP) 4 or later KSP. For CM 6.0.x, upgrade to CM 6.2 or later. |
| Avaya Aura® Conferencing Standard Edition | 6.x | Medium | See recommended actions 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.0, 5.1 | Low | Upgrade to Avaya IQ 5.2 or later. |
| Avaya Aura® Presence Services | 6.0, 6.1, 6.1.1 | Medium | Upgrade to PS 6.1.2 or later. |
| Avaya Aura® Session Manager | 1.1, 5.2, 6.0 | Medium | Upgrade to SM 6.1 or later. |
| Avaya Aura® System Manager | 5.2, 6.0, 6.1, 6.1.1 | Medium | Upgrade to SMGR 6.1.2 or later. |
| Avaya Aura® System Platform | 1.1, 6.0 including 6.0 SP1 | Medium | Upgrade to SP 6.0 SP2 (6.0.2.0.5) or later. |
| Avaya Voice Portal | 5.0, 5.1 including SP1 | Medium | Upgrade to Avaya Enterprise Linux for VP 5.1 SP2 and VP 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's
product and the surrounding network from this potential
vulnerability may be mitigated by ensuring these
practices are implemented until such time as a product
update is available or the recommended action is applied.
Further restrictions as deemed necessary based on the
customer's security policies may be required during this
interim period.
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 RedHat 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 15, 2010 - Initial Statement issued.
V 2.0 - February 1, 2011 - Changed AES actions.
V 3.0 - March 10, 2011 - Changed SM and SP actions, and SP affected versions.
V 4.0 - September 21, 2011 - Changed IQ and SMGR affected versions and actions.
V 5.0 - December 15, 2011 - Changed VP affected versions, and CM and VP actions.
V 6.0 - April 4, 2012 - Changed CM and PS affected versions and actions.
V 7.0 - June 26, 2013 - Changed Conferencing SE 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 securityalerts@avaya.com.
© 2010 Avaya Inc. All Rights Reserved. All trademarks identified by the ® or ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.