Secure-world kernel crash via miscast shared-memory buffer
Published Jun 3, 2026 · Updated Jun 3, 2026
Type confusion in OP-TEE OS 4.3.0 through 4.10.0 allows attackers to crash the S-EL1 kernel via a crafted FFA_MEM_SHARE request. handle_mem_op_tmem passes an attacker-controlled dynamic buffer to spmc_sp_add_share as a struct ffa_rxtx, causing its rx field to be dereferenced as an address. Exploitation requires EL1 Normal World control and both SPMC configuration options; the panic can disrupt a hypervisor and its guests.
Summary
What happened
Type confusion in OP-TEE OS 4.3.0 through 4.10.0 allows attackers to crash the S-EL1 kernel via a crafted FFA_MEM_SHARE request. handle_mem_op_tmem passes an attacker-controlled dynamic buffer to spmc_sp_add_share as a struct ffa_rxtx, causing its rx field to be dereferenced as an address. Exploitation requires EL1 Normal World control and both SPMC configuration options; the panic can disrupt a hypervisor and its guests.
The record
- CVE
- CVE-2026-45702
- Published
- Jun 3, 2026
- Updated
- Jun 3, 2026
- Vendor
- OP-TEE
- Product
- OP-TEE OS
- Classifications
- CWE-843, T1499
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 3, 2026CVE publishedPublication date reported by the CVE source.
- Jun 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 4.3.0, < 4.11.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo