Android kernel vulnerabilities

CVE-2017-13174 is a privilege escalation vulnerability in the Android kernel. It affects Android kernel versions and may allow unauthorized access to system resources.

CVE-2017-13168 is a privilege escalation vulnerability in the Android kernel SCSI driver. It affects the Android kernel in versions related to Android ID A-65023233.

CVE-2017-13167 describes an elevation of privilege vulnerability in the kernel sound timer of Android. It affects the Android kernel in versions that do not include patches.

An elevation of privilege vulnerability in the Android kernel file system. Affects the Android kernel (Android ID A-31269937).

An information disclosure vulnerability in the kernel binder driver of Android. It affects the Android kernel and may lead to unauthorized access to sensitive data.

CVE-2017-13163 is a privilege escalation vulnerability in the MTP USB driver in the Android kernel. It affects Android kernel versions.

CVE-2017-13162 is a privilege escalation vulnerability in the Android kernel, which may allow unauthorized access to system resources.

CVE-2017-0864 is a privilege escalation vulnerability in the MediaTek ioctl (flashlight) in Android. It affects the Android kernel.

CVE-2017-0862 is a privilege escalation vulnerability in the Android kernel. It affects unspecified versions of the Android kernel.

CVE-2017-0794 is a privilege escalation vulnerability in the Upstream kernel SCSI driver. It affects the Android operating system and its kernel.

An elevation of privilege vulnerability in the Upstream Linux file system. It affects Android kernels.

CVE-2017-0749 is a privilege escalation vulnerability in the Linux kernel used in Android. It affects the Android kernel versions.

A privilege escalation vulnerability in the Android kernel related to the Upstream Linux tcb component.

CVE-2017-0528 describes an elevation of privilege vulnerability in the kernel security subsystem that allows a local malicious application to execute code in the context of a privileged process. This issue is rated as High due to being a general bypass for kernel level defense mechanisms.

A vulnerability in the FIQ debugger of the kernel allows a local malicious application to execute arbitrary code within the kernel context. This issue is rated as Critical due to the potential for permanent device compromise.

Possible unauthorized memory access in the hypervisor. Incorrect configuration provides access to subsystem page tables.

Possible unauthorized memory access in the hypervisor. Lack of input validation could allow hypervisor memory to be accessed by the HLOS.

Android before 2016-08-05 does not properly restrict code execution in a kernel context, allowing attackers to gain privileges via a crafted application.

The prctl_set_vma_anon_name function in Android before version 5.1.1 LMY49F and 6.0 before January 1, 2016, does not ensure that only one vma is accessed in a certain update action, allowing attackers to gain privileges or cause a denial of service (vma list corruption) via a crafted application.

Possible buffer overflow in storage subsystem. Bad parameters as part of listener responses to RPMB commands could lead to buffer overflow.

Possible buffer overflow in SMMU system call. Improper input validation in ADSP SID2CB system call may result in hypervisor memory overwrite.

Possible buffer overflow in trust zone access control API. Buffer overflow may occur due to lack of buffer size checking.

Integer overflow leads to a TOCTOU condition in hypervisor PIL. This overflow can be exploited to bypass (Peripheral Image Loader) PIL authentication.

Improper input validation in Access Control APIs may lead to incorrect memory range checking. The issue affects the kernel version 3.18.

Unauthenticated messages are processed by the User Equipment (UE). Certain NAS messages are processed when no EPS security context exists in the UE.

In the Android kernel, in verity_target of dm-verity-target.c, a missing permission check allows modification of read-only files. This could lead to local privilege escalation with System execution privileges. User interaction is not needed.

In l2cap_chan_put of l2cap_core, there is a possible use-after-free due to improper locking. This could lead to local privilege escalation without additional execution privileges or user interaction.

In emulation_proc_handler of armv8_deprecated.c, there is a possible way to corrupt memory due to a race condition. This could lead to local privilege escalation without additional execution privileges or user interaction.

In binder_inc_ref_for_node of binder.c, there is a possible way to corrupt memory due to a use after free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

In lock_sock_nested in sock.c, a use-after-free is possible due to a race condition. This could lead to local privilege escalation with System execution privileges needed, without user interaction.

In rcu_cblist_dequeue of rcu_segcblist.c, there is a possible use-after-free due to improper locking. This could lead to local escalation of privilege in the kernel with System execution privileges needed. User interaction is not needed for exploitation. Product: Android, Versions: Android kernel.