TRUSTY · CVE-2026-56916 · Infrastructure
NO FIX YET
A time-of-check/time-of-use race in the Trusty kernel's virtqueue code (trusty/kernel/lib/trusty/vqueue.c) lets a local process read a value twice with different results. The description says this can lead to privilege escalation on the device.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
The sources describe a local attacker with execution privileges on a device running the Trusty secure OS kernel, which is typically found in Android phones and tablets. The sources do not list affected versions or whether specific devices are impacted, so teams cannot tell from the description alone whether they run it. Users who cannot run code locally are not described as exposed.
Not affected if no-local-code-execution
Who cares android, linux-kernel, trusty
Unknown from the sources.
No fix yet, per the sources.
In _vqueue_get_avail_buf_locked of trusty/kernel/lib/trusty/vqueue.c, there is a possible Double-read / TOCTOU due to a race condition. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.