# CVE-2026-56916: Google Trusty TOCTOU race condition in vqueue

Source: https://junglewise.ai/threats/cve-2026-56916-in-vqueue-get-avail-buf-locked-of-trusty-kernel-lib-trusty-vqueue  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-10. Updated: 2026-11-10  
License: CC BY 4.0 with a link back

CVE-2026-56916 · Severity: info · Published 2026-11-10

Trusty is Google's trusted execution environment that runs on Pixel devices to protect sensitive operations. A race condition in the virtual queue handler could allow a local attacker to escalate privileges within the trusted environment, potentially compromising secure system functions and protected data.

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

## Quick answers

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

**How severe is CVE-2026-56916?** Informational severity, published 10 November 2026.

**Which products and versions are affected?** Google Trusty.

**Is there a fix for CVE-2026-56916?** Yes: fixed in Pixel security patch level 2026-11-05 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

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

**Am I affected by CVE-2026-56916?** Check whether you run 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.

## How to fix

- Fixed in Pixel security patch level 2026-11-05 or later

## Technical details

A double-read / TOCTOU (time-of-check, time-of-use) race condition exists in _vqueue_get_avail_buf_locked within trusty/kernel/lib/trusty/vqueue.c. The vulnerability allows local escalation of privilege and requires user interaction for exploitation. A fix is available in the November 2026 Pixel security patch (2026-11-05 or later).

## Affected products

- Google Trusty

## Timeline

- 2026-11-10: disclosed

## References

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

## Related threats

- [Google Trusty out-of-bounds read via sign extension in shared memory](https://junglewise.ai/threats/cve-2026-55348-in-getsharedmemory-of-trusty-shared-memory-manager-cc-there-is-a)
- [ARM64_TLBI memory corruption in Trusty kernel](https://junglewise.ai/threats/cve-2026-58728-arm64-tlbi-memory-corruption-in-trusty-kernel)
- [Google Trusty out-of-bounds write via race condition](https://junglewise.ai/threats/cve-2026-58701-google-trusty-out-of-bounds-write-via-race-condition)
