CVE-2026-55348 · Infrastructure
NO FIX YET
A sign-extension error in the Trusty shared memory manager lets a negative buffer size cause an out-of-bounds read. An attacker with System-level code on the device could read memory they should not see.
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.
No product ranges from the sources yet.
Who cares android, trusty
Unknown from the sources.
No fix yet, per the sources.
In GetSharedMemory of trusty_shared_memory_manager.cc, there is a possible way to trigger an out of bounds read via sign extension of a negative buffer size due to an improper or implicit cast. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed 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.