Google

Android

8158 Schwachstellen gefunden.

Hinweis: Diese Liste kann unvollständig sein. Daten werden ohne Gewähr im Ursprungsformat bereitgestellt.
Medienbericht
  • EPSS 0.48%
  • Veröffentlicht 08.12.2025 17:16:19
  • Zuletzt bearbeitet 06.03.2026 04:15:59

In onHeaderDecoded of LocalImageResolver.java, there is a possible persistent denial of service due to resource exhaustion. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for...

  • EPSS 0.08%
  • Veröffentlicht 08.12.2025 17:16:19
  • Zuletzt bearbeitet 08.12.2025 20:15:51

In setDisplayName of AssociationRequest.java, there is a possible way to cause CDM associations to persist after the user has disassociated them due to improper input validation. This could lead to local escalation of privilege with no additional exe...

Warnung Medienbericht
  • EPSS 0.25%
  • Veröffentlicht 08.12.2025 17:16:19
  • Zuletzt bearbeitet 10.12.2025 02:00:02

In hasAccountsOnAnyUser of DevicePolicyManagerService.java, there is a possible way to add a Device Owner after provisioning due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges ne...

  • EPSS 0.1%
  • Veröffentlicht 08.12.2025 17:16:19
  • Zuletzt bearbeitet 11.12.2025 15:15:48

In multiple functions of mem_protect.c, there is a possible out of bounds write due to an integer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitati...

  • EPSS 0.1%
  • Veröffentlicht 08.12.2025 17:16:19
  • Zuletzt bearbeitet 08.12.2025 20:15:51

In __pkvm_load_tracing of trace.c, there is a possible out-of-bounds write due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitat...

  • EPSS 0.09%
  • Veröffentlicht 08.12.2025 17:16:19
  • Zuletzt bearbeitet 08.12.2025 20:15:52

In DefaultTransitionHandler.java, there is a possible way to unknowingly grant permissions to an app due to a tapjacking/overlay attack. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction...

  • EPSS 0.1%
  • Veröffentlicht 08.12.2025 17:16:18
  • Zuletzt bearbeitet 01.06.2026 22:16:18

In getComponentName of MediaButtonReceiverHolder.java, there is a possible desync in persistence due to resource exhaustion. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not need...

  • EPSS 0.12%
  • Veröffentlicht 08.12.2025 17:16:18
  • Zuletzt bearbeitet 08.12.2025 20:15:50

In processLaunchBrowser of CommandParamsFactory.java, there is a possible browser interaction from the lockscreen due to improper locking. This could lead to physical escalation of privilege with no additional execution privileges needed. User intera...

  • EPSS 0.09%
  • Veröffentlicht 08.12.2025 17:16:18
  • Zuletzt bearbeitet 08.12.2025 21:16:01

In onSomePackagesChanged of VoiceInteractionManagerService.java, there is a possible way for a third party application's component name to persist even after uninstalling due to a logic error in the code. This could lead to local escalation of privil...

  • EPSS 0.13%
  • Veröffentlicht 08.12.2025 17:16:18
  • Zuletzt bearbeitet 08.12.2025 20:15:50

In DefaultTransitionHandler.java, there is a possible way to enable a tapjacking attack due to a insecure default. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploit...