Steven Vittitoe

**Name of the Vulnerable Software and Affected Versions** Microsoft Office software (affected versions not specified) **Description** The issue is caused by a buffer overflow in memory, allowing a remote attacker to execute arbitrary code or cause a denial of service (memory corruption) by using a specially crafted document. An attacker who successfully exploits the issue could run arbitrary code in the context of the current user. If the current user has administrative rights, the attacker could take control of the affected system, install programs, view, change, or delete data, or create new accounts with full user rights. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Linux kernel versions through 3.16.3 **Description** The issue is related to multiple stack-based buffer overflows in the `magicmouse raw event` function in the Magic Mouse HID driver. This allows physically proximate attackers to cause a denial of service (system crash) or possibly execute arbitrary code via a crafted device that provides a large amount of (1) EHCI or (2) XHCI data associated with an event. **Recommendations** For Linux kernel versions through 3.16.3, update to a version later than 3.16.3 to resolve the issue. As a temporary workaround, consider restricting access to the `magicmouse raw event` function in the Magic Mouse HID driver to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Linux kernel versions through 3.16.3 **Description** The issue allows physically proximate attackers to cause a denial of service or possibly execute arbitrary code via a crafted device that sends a large report, exploiting a buffer overflow in the `picolcd raw event` function in the PicoLCD HID device driver. This is particularly relevant in Android on Nexus 7 devices. **Recommendations** For Linux kernel versions through 3.16.3, update to a version later than 3.16.3 to resolve the issue. As a temporary workaround, consider restricting access to the PicoLCD HID device driver to minimize the risk of exploitation.