The kernel packages contain the Linux kernel, the core of any Linux operating system.
This update fixes the following security issues:
* a NULL pointer dereference flaw was found in the sctp_rcv_ootb() function in the Linux kernel Stream Control Transmission Protocol (SCTP) implementation. A remote attacker could send a specially-crafted SCTP packet to a target system, resulting in a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-0008 to this issue.
* a NULL pointer dereference flaw was found in the Linux kernel. During a core dump, the kernel did not check if the Virtual Dynamically-linked Shared Object page was accessible. On Intel 64 and AMD64 systems, a local, unprivileged user could use this flaw to cause a kernel panic by running a crafted 32-bit application. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2009-4271 to this issue.
* an information leak was found in the print_fatal_signal() implementation in the Linux kernel. When "/proc/sys/kernel/print-fatal-signals" is set to 1 (the default value is 0), memory that is reachable by the kernel could be leaked to user-space. This issue could also result in a system crash. Note that this flaw only affected the i386 architecture. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-0003 to this issue.
* on AMD64 systems, it was discovered that the kernel did not ensure the ELF interpreter was available before making a call to the SET_PERSONALITY macro. A local attacker could use this flaw to cause a denial of service by running a 32-bit application that attempts to execute a 64-bit application. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-0307 to this issue.
* missing capability checks were found in the ebtables implementation, used for creating an Ethernet bridge firewall. This could allow a local, unprivileged user to bypass intended capability restrictions and modify ebtables rules. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-0007 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||4.0 thru 4.2.3||Low||Upgrade to AES 4.2.4 or later.|
|Avaya Aura™ Communication Manager||5.1.x and earlier||Low||Upgrade to CM 5.2 or later|
|Avaya Intuity AUDIX LX||2.0.x||Low||This advisory will not be addressed by Intuity AUDIX LX as no further releases are planned.|
|Avaya Meeting Exchange||5.x||Low||Upgrade to MX 6.2 or later.|
|Avaya Message Networking||3.1, 5.2 thru 5.2.2||Low||Upgrade to MN 5.2.3 or later|
|Avaya Messaging Storage Server||4.x, 5.2 thru 5.2.7||Low||Upgrade to MM 5.2.8 or later|
|Avaya Aura™ SIP Enablement Services||5.1.x and earlier||Low||See recommended actions below. This advisory will not be addressed by SES as no further releases are planned.|
|Avaya Proactive Contact||4.0, 4.1, 4.1.x, 4.2||Low||Upgrade to PC 4.2.1 or later.|
|Avaya Voice Portal||4.x||Low||Upgrade to VP 5.0 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.
|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™ 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 - April 16, 2010 - Initial Statement issued.
V 2.0 - August 12, 2010 - Changed AES affected versions and actions.
V 3.0 - December 23, 2010 - Changed PC actions and affected versions.
V 4.0 - July 15, 2011 - Changed actions and affected versions for CM, MN, MSS and VP.
V 5.0 - March 15, 2013 - Changed MX 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 firstname.lastname@example.org.
© 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.