ALAS-2015-523

Related Vulnerabilities: CVE-2015-3331   CVE-2015-3636  

A buffer overflow flaw was found in the way the Linux kernel's Intel AES-NI instructions optimized version of the RFC4106 GCM mode decryption functionality handled fragmented packets. A remote attacker could use this flaw to crash, or potentially escalate their privileges on, a system over a connection with an active AEC-GCM mode IPSec security association. (CVE-2015-3331) It was found that the Linux kernel's ping socket implementation did not properly handle socket unhashing during spurious disconnects, which could lead to a use-after-free flaw. On x86-64 architecture systems, a local user able to create ping sockets could use this flaw to crash the system. On non-x86-64 architecture systems, a local user able to create ping sockets could use this flaw to escalate their privileges on the system. (CVE-2015-3636)

ALAS-2015-523


Amazon Linux AMI Security Advisory: ALAS-2015-523
Advisory Release Date: 2015-05-14 14:27 Pacific
Advisory Updated Date: 2015-05-14 23:48 Pacific
Severity: Medium

Issue Overview:

A buffer overflow flaw was found in the way the Linux kernel's Intel AES-NI instructions optimized version of the RFC4106 GCM mode decryption functionality handled fragmented packets. A remote attacker could use this flaw to crash, or potentially escalate their privileges on, a system over a connection with an active AEC-GCM mode IPSec security association. (CVE-2015-3331)

It was found that the Linux kernel's ping socket implementation did not properly handle socket unhashing during spurious disconnects, which could lead to a use-after-free flaw. On x86-64 architecture systems, a local user able to create ping sockets could use this flaw to crash the system. On non-x86-64 architecture systems, a local user able to create ping sockets could use this flaw to escalate their privileges on the system. (CVE-2015-3636)


Affected Packages:

kernel


Issue Correction:
Run yum clean all followed by yum update kernel to update your system. You will need to reboot your system in order for the new kernel to be running.

New Packages:
i686:
    kernel-3.14.42-31.38.amzn1.i686
    perf-debuginfo-3.14.42-31.38.amzn1.i686
    kernel-tools-devel-3.14.42-31.38.amzn1.i686
    kernel-tools-debuginfo-3.14.42-31.38.amzn1.i686
    kernel-tools-3.14.42-31.38.amzn1.i686
    perf-3.14.42-31.38.amzn1.i686
    kernel-debuginfo-3.14.42-31.38.amzn1.i686
    kernel-debuginfo-common-i686-3.14.42-31.38.amzn1.i686
    kernel-headers-3.14.42-31.38.amzn1.i686
    kernel-devel-3.14.42-31.38.amzn1.i686

noarch:
    kernel-doc-3.14.42-31.38.amzn1.noarch

src:
    kernel-3.14.42-31.38.amzn1.src

x86_64:
    kernel-3.14.42-31.38.amzn1.x86_64
    kernel-debuginfo-common-x86_64-3.14.42-31.38.amzn1.x86_64
    kernel-debuginfo-3.14.42-31.38.amzn1.x86_64
    perf-debuginfo-3.14.42-31.38.amzn1.x86_64
    kernel-tools-debuginfo-3.14.42-31.38.amzn1.x86_64
    kernel-devel-3.14.42-31.38.amzn1.x86_64
    kernel-headers-3.14.42-31.38.amzn1.x86_64
    kernel-tools-devel-3.14.42-31.38.amzn1.x86_64
    kernel-tools-3.14.42-31.38.amzn1.x86_64
    perf-3.14.42-31.38.amzn1.x86_64