The kernel packages contain the Linux kernel, the core of any Linux operating system.
Security fixes:
* a race condition was found in the mac80211 implementation, a framework used for writing drivers for wireless devices. An attacker could trigger this flaw by sending a Delete Block ACK (DELBA) packet to a target system, resulting in a remote denial of service. Note: This issue only affected users on 802.11n networks, and that also use the iwlagn driver with Intel wireless hardware. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2009-4027 to this issue.
* a use-after-free flaw was found in the tcp_rcv_state_process() function in the Linux kernel TCP/IP protocol suite implementation. If a system using IPv6 had the IPV6_RECVPKTINFO option set on a listening socket, a remote attacker could send an IPv6 packet to that system, causing a kernel panic (denial of service). The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-1188 to this issue.
* a flaw was found in the gfs2_lock() implementation. The GFS2 locking code could skip the lock operation for files that have the S_ISGID bit (set-group-ID on execution) in their mode set. A local, unprivileged user on a system that has a GFS2 file system mounted could use this flaw to cause a kernel panic (denial of service). The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-0727 to this issue.
* a divide-by-zero flaw was found in the ext4 file system code. A local attacker could use this flaw to cause a denial of service by mounting a specially-crafted ext4 file system. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2009-4307 to this issue.
More information about these vulnerabilities can be found in the security advisories issued by RedHat Linux:
| Product: | Affected Version(s): | Risk Level: | Actions: |
|---|---|---|---|
| Avaya Aura® Application Enablement Services | AES 5.2, 5.2.1 | Low | Upgrade to AES 5.2.2 or later. |
| Avaya Aura® Communication Manager | CM 5.2, 5.2.x | Low | Upgrade to CM 5.2.1 with Kernel Service Pack 2.6.18-128Ak03 or later installed or upgrade to CM6.0.1 |
| Avaya IQ | IQ 5.0, 5.0.x, 5.1.x | Low | Upgrade to IQ 5.2 or later. |
| Avaya Aura® Session Manager | SM 1.1, 5.2, 6.0 | Low | Upgrade to SM 6.1 or later. |
| Avaya Aura® SIP Enablement Services | SES 5.2, 5.2.x | Low | See recommended actions below. This advisory will not be addressed by SIP Enablement Services as no further releases are planned. |
| Avaya Aura® System Manager | SMGR 5.2, 6.0, 6.1 | Low | For SMGR 5.2 or 6.0, upgrade to SMGR 6.0 with SP1 or later. For SMGR 6.1, upgrade to SMGR 6.1 with SP1 or later. |
| Avaya Aura® System Platform | SP 1.1, 6.0 | Low | Upgrade to SP 6.0 with Service Pack 3 or later. |
| Avaya Voice Portal | VP 5.0 | Low | Upgrade to VP 5.1 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 - May 11, 2010 - Initial Statement issued.
V 2.0 - September 16, 2010 - Updated CM Actions.
V 3.0 - October 11, 2010 - Updated CM Actions.
V 4.0 - June 21, 2011 - Updated IQ, SM, and VP Actions.
V 5.0 - June 22, 2011 - Added new RHSA advisory link.
V 6.0 - July 8, 2011 - Updated AES Actions.
V 7.0 - July 8, 2011 - Corrected AES Actions.
V 8.0 - July 12, 2011 - Updated SP, SMGR Actions and ASA 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.