Google

Pixel

4 Schwachstellen gefunden.

Hinweis: Diese Liste kann unvollständig sein. Daten werden ohne Gewähr im Ursprungsformat bereitgestellt.
  • EPSS 0.02%
  • Veröffentlicht 10.03.2026 20:46:53
  • Zuletzt bearbeitet 11.03.2026 17:13:25

There is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

  • EPSS 0.03%
  • Veröffentlicht 10.03.2026 19:33:06
  • Zuletzt bearbeitet 16.03.2026 14:17:59

In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

  • EPSS 0.02%
  • Veröffentlicht 05.04.2024 20:15:08
  • Zuletzt bearbeitet 17.06.2025 20:46:09

In tmu_set_temp_lut of tmu.c, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

  • EPSS 0.02%
  • Veröffentlicht 05.04.2024 20:15:08
  • Zuletzt bearbeitet 17.06.2025 20:48:18

In tmu_set_control_temp_step of tmu.c, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploita...