AUGUST 21, 2026
Live Feed
Back to database
Case File

CVE-2026-42546

LOW · CVSS 3.8 EPSS 0.10% Public Exploit

Source: NVD + CISA KEV + EPSS · Published 2026-07-06 · Last synced 2026-08-05

CyberRota Analysis

AI-Generated

The vulnerability affects OP-TEE, a Trusted Execution Environment for Linux running on Arm Cortex-A cores, specifically versions 3.3.0 to 4.10.0. It involves a resource leak in the shared memory cleanup logic that can lead to degraded system performance and potential service interruptions due to accumulated memory leaks, ultimately necessitating a reboot. Organizations utilizing OP-TEE in non-FF-A configurations should prioritize upgrading to version 4.11.0 to mitigate this issue, as no workarounds are available.

Public Exploit Signal

A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.

GitHub PoC Links

Note: these links are listed for security research and verification purposes only.

CVE
CVE-2026-42546
Severity
LOW
CVSS
3.8
EPSS
0.10%
Linux

Original NVD 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 3.3.0 and prior to version 4.11.0, a resource leak exists in OP-TEE’s shared memory cleanup logic because the function `cleanup_shm_refs()` in `core/tee/entry_std.c` fails to apply a required bitmask (`OPTEE_MSG_ATTR_TYPE_MASK`) to parameter attributes. When processing non-contiguous memory parameters from a normal-world caller, the system fails to match the attribute type in its internal switch statement and skips the necessary mobj_put() call. This results in a persistent reference leak of `mobj_reg_shm` objects, which remain on internal lists with dangling refcounts. This affects non-FF-A configurations that support non-contiguous, non-secure shared memory. Over time, these accumulated leaks progressively consume the secure-world heap, degrading the system's ability to service trusted application operations and eventually requiring a reboot to recover. Version 4.11.0 contains a patch. No known workarounds are available.

Related CVEs

Other vulnerabilities affecting the same vendor(s)