Quick answers
- Is CVE-2026-58728 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58728 being exploited in the wild.
- How severe is CVE-2026-58728?
- High severity, with a CVSS score of 7, published 15 September 2026.
- Which products and versions are affected?
- Google Trusty.
- Is there a fix for CVE-2026-58728?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-58728 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-58728?
- Check whether you run Google Android or Google Trusty. 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 in the ARM64_TLBI function (part of the memory management unit handling in mmu.h) within Trusty can lead to memory corruption. The vulnerability stems from improper synchronization during TLB (Translation Lookaside Buffer) invalidation operations, allowing concurrent access to kernel memory structures. This race condition is exploitable from a local context without additional execution privileges, enabling privilege escalation within the Trusty secure environment. The vulnerability is addressed through patching the synchronization logic in ARM64_TLBI operations.
Affected products
- Google Trusty
Timeline
- 2026-09-15: disclosed: Published in Pixel Update Bulletin and NVD