Google Android.

In RGXDestroyZSBufferKM of rgxta3d.c, there is a possible arbitrary code execution due to an uncaught exception.

• Google Android

In MMU_UnmapPages of mmu_common.c, there is a possible out of bounds read due to improper input validation.

• Google Android

In DevmemIntChangeSparse of devicemem_server.c, there is a possible out of bounds write due to an integer overflow.

• Google Android

In OSMMapPMRGeneric of pmr_os.c, there is a possible out of bounds write due to an uncaught exception.

• Google Android

In PMRChangeSparseMemOSMem of physmem_osmem_linux.c, there is a possible out of bounds write due to an incorrect bounds check.

• Google Android

In HTBLogKM of htbserver.c, there is a possible information disclosure due to log information disclosure.

• Google Android

In PMRChangeSparseMemOSMem of physmem_osmem_linux.c, there is a possible out of bounds write due to an incorrect bounds check.

• Google Android

In PMRWritePMPageList of TBD, there is a possible out of bounds write due to an integer overflow.

• Google Android

Incorrect default permissions in Google Android

• Google Android
• Broken access control

In DevmemIntAcquireRemoteCtx of devicemem_server.c, there is a possible arbitrary code execution due to a race condition.

• Google Android

In RGXBackingZSBuffer of rgxta3d.c, there is a possible arbitrary code execution due to a use after free.

• Google Android

In DevmemIntMapPMR of devicemem_server.c, there is a possible arbitrary code execution due to a use after free.

• Google Android

In PMR_ReadBytes of pmr.c, there is a possible arbitrary code execution due to a use after free.

• Google Android

In RGXUnbackingZSBuffer of rgxta3d.c, there is a possible arbitrary code execution due to a use after free.

• Google Android

Code injection in Google Android

• Google Android
• Code injection

Elevation of privilege

• Google Android

Information disclosure

• Google Android

Elevation of privilege

• Google Android

Remote code execution

• Google Android

Remote code execution

• Google Android

In Print Service, there is a possible background activity launch due to a logic error in the code.

• Google Android

In collapse of canonicalize_md.c, there is a possible out of bounds read due to a missing bounds check.

• Google Android

In sdksandbox, there is a possible strandhogg style overlay attack due to a logic error in the code.

• Google Android

Improper privilege management in Google Android

• Google Android
• Privilege escalation

Improper privilege management in Google Android

• Google Android
• Privilege escalation

In Bluetooth, there is a possible out of bounds read due to a use after free.

• Google Android

In registerPhoneAccount of TelecomServiceImpl.java, there is a possible way to reveal images from another user due to a missing permission check.

• Google Android

In Settings, there is a possible way for the user to change SIM due to a missing permission check.

• Google Android

In Bluetooth, there is a possible way to corrupt memory due to a use after free.

• Google Android

In Messaging, there is a possible way to disable the messaging application due to improper input validation.

• Google Android

Incorrect authorization in Google Android

• Google Android
• Broken access control

In Settings, there is a possible bypass of profile owner restrictions due to a missing permission check.

• Google Android

In Settings, there is a possible restriction bypass due to a missing permission check.

• Google Android

In User Backup Manager, there is a possible way to leak a token to bypass user confirmation for backup due to log information disclosure.

• Google Android

In Whitechapel, there is a possible out of bounds read due to memory corruption.

• Google Android

In Package Manager, there is a possible possible permissions bypass due to an unsafe PendingIntent.

• Google Android

In Settings, there is a possible way for the user to unintentionally send extra data due to an unclear prompt.

• Google Android

In Content Resolver, there is a possible method to access metadata about existing content providers on the device due to a missing permission check.

• Google Android

In Media Resource Manager, there is a possible local arbitrary code execution due to use after free.

• Google Android

In Bluetooth, there is a possible out of bounds write due to a heap buffer overflow.

• Google Android

In Bluetooth, there is a possible out of bounds read due to a missing bounds check.

• Google Android

In Telecomm, there is a possible way to silence the ring for calls of secondary users due to a missing permission check.

• Google Android

In SELinux Policy, there is a possible restriction bypass due to a permissions bypass.

• Google Android

Improper privilege management in Google Android

• Google Android
• Privilege escalation

In Sysproxy, there is a possible out of bounds write due to an integer underflow.

• Google Android

Improper privilege management in Google Android

• Google Android
• Privilege escalation

In Telephony, there is a possible way for a guest user to change the preferred SIM due to a missing permission check.

• Google Android

In libdexfile, there is a possible out of bounds read due to a missing bounds check.

• Google Android

In Secure Element, there is a possible out of bounds write due to an integer overflow.

• Google Android

In the Security Element API, there is a possible out of bounds write due to an integer overflow.

• Google Android

In Usage Access, there is a possible way to display a Settings usage access restriction toggle screen due to a permissions bypass.

• Google Android

In Audio, there is a possible out of bounds read due to missing bounds check.

• Google Android

In Scudo, there is a possible way to exploit certain heap OOB read/write issues due to an insecure implementation/design.

• Google Android

In Scudo, there is a possible way for an attacker to predict heap allocation patterns due to insecure implementation/design.

• Google Android

In Contacts, there is a possible crash loop due to resource exhaustion.

• Google Android

In ContactsProvider, there is a possible crash loop due to resource exhaustion.

• Google Android

In Usage, there is a possible permanent DoS due to resource exhaustion.

• Google Android

In Bluetooth, there is a possibility of code-execution due to a use after free.

• Google Android

In Bluetooth, there is a possible out of bounds write due to improper input validation.

• Google Android

In Bluetooth, there is a possible out of bounds read due to a missing bounds check.

• Google Android