Google

In NFC, there is a possible out of bounds read due to uninitialized data. This could lead to remote information disclosu

In Bluetooth, there is a possible spoofing of bluetooth device metadata due to a missing permission check. This could le

In Bluetooth, there is a possible control over Bluetooth enabled state due to a missing permission check. This could lea

In Telecom, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to local information d

In bindWallpaperComponentLocked of WallpaperManagerService.java, there is a possible permission bypass due to an unsafe

In Bluetooth, there is a possible out of bounds read due to a missing bounds check. This could lead to local information

In Bluetooth, there is a possible out of bounds read due to a missing bounds check. This could lead to local information

In Bluetooth AVRCP, there is a possible leak of audio metadata due to residual data. This could lead to remote informati

In Telephony, there is a possible permission bypass due to a missing permission check. This could lead to local informat

In Telephony, there is a possible permission bypass due to a missing permission check. This could lead to local informat

In NFC, there is a possible out of bounds read due to a missing bounds check. This could lead to remote information disc

In NFC, there is a possible out of bounds read due to a missing bounds check. This could lead to remote information disc

In Telephony, there is a possible permission bypass due to a missing permission check. This could lead to local informat

In hwservicemanager, there is a possible out of bounds write due to freeing a wild pointer. This could lead to local esc

In libhwbinder, there is a possible information disclosure due to uninitialized data. This could lead to local informati

In the Settings app, there is an insecure default value. This could lead to local escalation of privilege and tapjacking

In Android Auto Settings, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to local

In NFC, there is a possible use-after-free due to a race condition. This could lead to local escalation of privilege wit

In Telephony, there are possible leaks of sensitive data due to missing permission checks. This could lead to local info

In the Accessibility service, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to l

NVIDIA GeForce NOW, versions prior to 2.0.23 (Windows, macOS) and versions prior to 5.31 (Android, Shield TV), contains

In Bluetooth, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code exec

In the System UI, there is a possible system crash due to an uncaught exception. This could lead to local permanent deni

In WiFi tethering, there is a possible attacker controlled intent due to an unsafe PendingIntent. This could lead to loc

In the audio server, there is a missing permission check. This could lead to local escalation of privilege regarding aud

In SyncManager, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to local informati

There is a possible way to view notifications even when the "Lockdown" feature is on. This could lead to local informati

In libmpeg2dec, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalati

In Telephony, there is a possible permission bypass due to a missing permission check. This could lead to local escalati

In NFC, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to local escalation of pri

In SoundTriggerHwService, there is a possible out of bounds read due to a race condition. This could lead to local infor

In ActivityManager, there is a possible access to protected data due to a missing permission check. This could lead to l

In libAACdec, there is a possible out of bounds read due to missing bounds check. This could lead to remote information

In libavb, there is a possible out of bounds write due to an integer overflow. This could lead to local escalation of pr

In PackageInstaller, there is a possible permissions bypass due to a tapjacking vulnerability. This could lead to local

In libDRCdec, there is a possible out of bounds read due to a missing bounds check. This could lead to remote informatio

In libmedia, there is a possible resource exhaustion due to improper input validation. This could lead to remote denial

In libstagefright, there is a possible resource exhaustion due to improper input validation. This could lead to remote d

In libDRCdec, there is a possible information disclosure due to uninitialized data. This could lead to remote informatio

In Notification Access Confirmation, there is a possible permissions bypass due to uninformed consent. This could lead t

In GLESRenderEngine, there is a possible out of bounds read due to a buffer overflow. This could lead to local informati

In SurfaceFlinger, there is a possible use after free due to a race condition. This could lead to local escalation of pr

In SurfaceFlinger, there is a possible use-after-free due to improper locking. This could lead to local escalation of pr

In the Audio HAL, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local esc

In libFraunhoferAAC, there is a possible out of bounds read due to a missing bounds check. This could lead to remote inf

In libmp4extractor, there is a possible resource exhaustion due to a missing bounds check. This could lead to remote den

In MediaProvider, there is a possible permissions bypass due to SQL injection. This could lead to local information disc

In libstagefright, there is possible CPU exhaustion due to improper input validation. This could lead to remote denial o

In Mediaserver, there is a possible out of bounds write due to an integer overflow. This could lead to local escalation

In DocumentsUI, there is a possible permission bypass due to a confused deputy. This could lead to local escalation of p