The kernel packages contain the Linux kernel, the core of any Linux operating system.
This update fixes the following security issues:
* A missing boundary check was found in the dvb_ca_ioctl() function in the Linux kernel's av7110 module. On systems that use old DVB cards that require the av7110 module, a local, unprivileged user could use this flaw to cause a denial of service or escalate their privileges. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-0521 to this issue.
* An inconsistency was found in the interaction between the Linux kernel's method for allocating NFSv4 (Network File System version 4) ACL data and the method by which it was freed. This inconsistency led to a kernel panic which could be triggered by a local, unprivileged user with files owned by said user on an NFSv4 share. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1090 to this issue.
* A NULL pointer dereference flaw was found in the Generic Receive Offload (GRO) functionality in the Linux kernel's networking implementation. If both GRO and promiscuous mode were enabled on an interface in a virtual LAN (VLAN), it could result in a denial of service when a malformed VLAN frame is received on that interface. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1478 to this issue.
* A missing security check in the Linux kernel's implementation of the install_special_mapping() function could allow a local, unprivileged user to bypass the mmap_min_addr protection mechanism. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-4346 to this issue.
* An information leak was found in the Linux kernel's task_show_regs() implementation. On IBM S/390 systems, a local, unprivileged user could use this flaw to read /proc/[PID]/status files, allowing them to discover the CPU register values of processes. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-0710 to this issue.
* A missing validation check was found in the Linux kernel's mac_partition() implementation, used for supporting file systems created on Mac OS operating systems. A local attacker could use this flaw to cause a denial of service by mounting a disk that contains specially-crafted partitions. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1010 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 Aura® Application Enablement Services | 5.2.x, 6.1, 6.1.1 | Low | For Application Enablement Services 5.2 before 5.2.4, upgrade to 5.2.4 or later. |
Avaya Aura® Application Server 5300:
|
2.0 | Medium | Upgrade to AS5300 2.0 PB14 or later. |
| Avaya Aura® Communication Manager | 5.2, 5.2.1, 6.0.1 | Low | CM 5.2, 5.2.1: Upgrade to CM5.2.1 SP5 or later. CM6.0.1: Upgrade to CM 6.2 or later. |
Avaya Communication Server 1000:
|
6.0 through 7.5 | Low | Upgrade to 7.6 or later. |
| Avaya Aura® Conferencing Standard Edition | 6.0 including 6.0 SP1 | Medium | See recommended actions and Mitigating Factors table 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 IP Office Application Server | 6.0, 6.1, 7.0 | Medium | Upgrade to IP Office Application Server 8.1 or later. |
| Avaya IQ | 5.2 thru 5.2.5 | Medium | Upgrade to 5.2.6 and install Patch 2 or later. |
| Avaya Aura® Presence Services | 6.0, 6.1 | Medium | Upgrade to PS 6.1.2 or later. |
| Avaya Aura® Session Manager | 1.1, 5.2.x, 6.0.x, 6.1.x | Low | Upgrade to SM 6.1.5 or later. |
| Avaya Aura® System Manager | 5.2, 6.0.x, 6.1.x | Medium | Upgrade to SMGR 6.1 SP4 or later. |
| Avaya Aura® System Platform | 1.1, 6.0.x | Medium | Upgrade to SP 6.0 with Patch 6.0.3.6.3 or later. | Avaya Aura® Communication Manager Utility Services | 1.1, 6.0, 6.1 | None | No action required - see Mitigating Factors Table. |
| Avaya Voice Portal | 5.0.x, 5.1, 5.1.1 | Medium | Upgrade to VP 5.1.2 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
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 customers should not modify the System Product
operating system or application 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:
| Vulnerability | Mitigating Factors |
|---|---|
|
CVE-2010-4346 CVE-2011-0710 CVE-2011-1010 CVE-2011-1478 |
These are rated a Low for all products except Utility Services, which is rated a None since there is no customer shell access available. |
|
CVE-2011-0521 CVE-2011-1090 |
These are rated a Medium for all products except for AES, CM, CS1000 and SM (all Low) since the affected modules or drivers are not used or supported. These are rated a None for Utility Services since there is no customer shell access available. |
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 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 - June 20, 2011 - Initial Statement issued.
V 2.0 - January 10, 2012 - Updated SM, SMGR and VP Actions.
V 3.0 - March 5, 2012 - Updated AS5300, IP Office Application Server and PS Actions.
V 4.0 - April 13, 2012 - Updated CM, SMGR and SP actions.
V 5.0 - December 7, 2012 - Updated AES and IPO-AS actions.
V 6.0 - August 5, 2014 - Updated CS1000 and Conferencing Standard Edition actions.
V 7.0 - June 26, 2015 - Updated IQ affected versions and actions, and set 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 [email protected].
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
© 2011 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.