CVE-2026-58695
massMissing bounds check in Google device kernel PHY power code enables local EoP
A missing bounds check (CWE-120) in gmc_phy_lp3_exit_restore_registers of phy_power.c — code that restores PHY registers when the device exits the LP3 low-power state — allows a buffer overflow that leads to local escalation of privilege. It is triggered by code running locally on the device, with no user interaction required; the advisory states System execution privileges are needed for exploitation. A successful attacker gains elevated (kernel-context) execution on the device, with high impact on confidentiality, integrity and availability (CVSS 3.1 score 7.8, AV:L/PR:L). The CVE was assigned by Google's device-security CNA ([email protected]), indicating Google mobile device platforms, but the advisory does not name specific device models or a fixed version. No public proof-of-concept is known and the issue is not listed in CISA KEV, so exploitation has not been confirmed.
What to do: Apply the Google/Android (Pixel) security update that includes this fix once published — the advisory provides no fixed build number, so check the device's Android security patch level after updating. Until patched, reduce risk by avoiding installation of untrusted apps that can run local code on affected devices. No public exploit or KEV listing exists, so there are no specific indicators of compromise to hunt for; monitor Google's Android/Pixel security bulletins for the fixed release.
| Google Mobile device kernel — gmc PHY power driver (gmc_phy_lp3_exit_restore_registers, phy_power.c) | — |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
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.
- Weakness
- CWE-120
- Vector
- CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
In the news0 stories
No ingested article mentions this CVE yet.