CVE-2026-58695
published 2026-09-15CVE-2026-58695: In gmc_phy_lp3_exit_restore_registers of phy_power.c, there is a possible escalation of privilege due to a missing bounds check. This could lead to local…
PriorityP345high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.11%
1.7th percentile
In gmc_phy_lp3_exit_restore_registers of phy_power.c, there is a possible escalation of privilege due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| android | — | — |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
In gmc_phy_lp3_exit_restore_registers of phy_power.c, there is a possible escalation of privilege due to a missing bounds check.
ghsa_unreviewed·2026-09-15
CVE-2026-58695 [HIGH] CWE-120 In gmc_phy_lp3_exit_restore_registers of phy_power.c, there is a possible escalation of privilege due to a missing bounds check.
In gmc_phy_lp3_exit_restore_registers of phy_power.c, there is a possible escalation of privilege due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.
VulDB
Google Android phy_power.c gmc_phy_lp3_exit_restore_registers memory corruption
vuldb·2026-09-15
CVE-2026-58695 [CRITICAL] Google Android phy_power.c gmc_phy_lp3_exit_restore_registers memory corruption
A vulnerability was found in Google Android. It has been classified as critical. This affects the function gmc_phy_lp3_exit_restore_registers of the file phy_power.c. The manipulation leads to memory corruption.
This vulnerability is traded as CVE-2026-58695. An attack has to be approached locally. There is no exploit available.
Applying a patch is the recommended action to fix this issue.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2026-09-15
Published