# CVE-2026-58701: Google Trusty out-of-bounds write via race condition

Source: https://junglewise.ai/threats/cve-2026-58701-google-trusty-out-of-bounds-write-via-race-condition  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-15. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-58701 · Severity: high · CVSS 7 · Published 2026-09-15

Google Trusty is a secure execution environment that runs on Pixel devices to handle sensitive operations like fingerprint processing and hardware key management. A race condition in the trusty_dputc function allows a local attacker with system privileges to write data outside allocated memory bounds, potentially leading to unauthorized system control or data corruption.

Technologies: [Google Android](https://junglewise.ai/threats/technologies/android), [Google Trusty](https://junglewise.ai/threats/technologies/trusty). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

**Is CVE-2026-58701 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-58701 being exploited in the wild.

**How severe is CVE-2026-58701?** High severity, with a CVSS score of 7, published 15 September 2026.

**Which products and versions are affected?** Google Trusty Unspecified; patch available as of 2026-09-05 security patch level.

**Is there a fix for CVE-2026-58701?** A patch was published on 2026-09-05: Google Pixel devices received updates to 2026-09-05 patch level addressing this issue Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-58701 attacked?** It is attacked with local access, in device firmware.

**Am I affected by CVE-2026-58701?** Check whether you run Google Android or Google Trusty at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A race condition exists in the trusty_dputc function of generic-arm64-smcall.c in Google Trusty, leading to an out-of-bounds write vulnerability. The vulnerability is reachable locally with System execution privileges and does not require user interaction for exploitation. An attacker with system-level access can exploit this race condition to write beyond memory boundaries, achieving local privilege escalation within the Trusty environment.

## Affected products

- Google Trusty Unspecified; patch available as of 2026-09-05 security patch level

## Timeline

- 2026-09-15: disclosed
- 2026-09-05: patched: Google Pixel devices received updates to 2026-09-05 patch level addressing this issue

## References

- [https://source.android.com/docs/security/bulletin/pixel/2026/2026-09-01](https://source.android.com/docs/security/bulletin/pixel/2026/2026-09-01)

## Related threats

- [Google Android Bluetooth buffer overflow in acquireMemory](https://junglewise.ai/threats/cve-2026-95405-in-acquirememory-of-bt-bqr-offload-cc-there-is-a-possible-way-to)
- [ST NFC HAL out-of-bounds write in global memory](https://junglewise.ai/threats/cve-2026-95400-in-stnfc-hal-write-of-hal-st21nfc-cc-there-is-a-possible-way-to)
- [Android HEVC decoder buffer overflow in sub_layer_hrd_parameters](https://junglewise.ai/threats/cve-2026-95397-in-sub-layer-hrd-parameters-of-hevc-decoder-there-is-a-possible)
- [Android framework memory exhaustion in message queue handling](https://junglewise.ai/threats/cve-2026-59632-in-respondreceivedmessage-of-mtsmessagecontroller-cpp-there-is-a)
- [Android use-after-free in UssiController connection listener](https://junglewise.ai/threats/cve-2026-59626-in-sendinfo-of-ussicontroller-cpp-there-is-a-possible-way-to)