Samsung Vyond EUVD-2026-101869

Exploitation requires the ability to invoke the Keystone SBI create_enclave path in the Vyond TEE monitor (tee/monitor/src/enclave.rs) with a controlled enclave ID (eid) and to supply an eid >= MAX_ENCLAVES so the pre-patch ENCLAVES[eid] access runs out of bounds. Per the CVSS vector this is local (AV:L) and demands high privilege (PR:H) - i.e. the attacker must already operate supervisor-mode software that drives enclave creation; it is not reachable by a remote or unauthenticated attacker, and no end-user interaction is involved (UI:N). The impact is limited to availability (monitor crash/instability); there is no confidentiality or integrity effect. Only versions before commit be6e297b0c4836e20d73b2f8a40a561ea496ebaa are affected.

This is a genuinely low-priority issue despite being tracked as a CVE. The CVSS 3.1 vector (AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H, base 4.4 MEDIUM) describes a locally-exploitable, high-privilege flaw with no confidentiality or integrity impact and only an availability effect. The source-code evidence confirms this: the patched function create_enclave in tee/monitor/src/enclave.rs indexed the fixed-size ENCLAVES array with an attacker-influenced eid without a MAX_ENCLAVES bounds check (CWE-129), an out-of-bounds access that would crash or destabilize the TEE monitor. No EPSS score was supplied, there is no CISA KEV listing, and no public exploit was provided - only the upstream fix commit. All signals point in the same (low) direction: no exploitation evidence, local-only reachability, and a caller (the Keystone SBI create path invoked from supervisor-mode software) that already holds high privilege, so the attacker must effectively control the enclave-creation interface before triggering the bug. Note that the 'Information Disclosure' tag conflicts with the CVSS vector (C:N), which indicates no confidentiality impact - the real impact is availability, so that tag appears mislabeled and should not drive prioritization. EPSS is absent rather than low, so no probabilistic exploitation estimate is available.

A privileged component with access to the Keystone SBI enclave-creation interface (e.g. a compromised or malicious supervisor-mode OS/driver) invokes create_enclave with an enclave ID (eid) at or beyond MAX_ENCLAVES. The unchecked ENCLAVES[eid] access reads out of bounds, crashing or corrupting the TEE monitor and denying service to legitimate enclaves. No public proof-of-concept was provided - only the vendor fix commit is available.