VYPR
Unrated severityNVD Advisory· Published Sep 16, 2022· Updated Aug 3, 2024

CVE-2022-40761

CVE-2022-40761

Description

The function tee_obj_free in Samsung mTower through 0.3.0 allows a trusted application to trigger a Denial of Service (DoS) by invoking the function TEE_AllocateOperation with a disturbed heap layout, related to utee_cryp_obj_alloc.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A heap layout disturbance in Samsung mTower up to v0.3.0 allows a trusted application to trigger a denial-of-service via the function TEE_AllocateOperation.

Vulnerability

An improper input validation vulnerability exists in the tee_obj_free function in Samsung mTower through version 0.3.0 [1][3]. The flaw, related to utee_cryp_obj_alloc, occurs when a trusted application invokes TEE_AllocateOperation with a specially crafted heap layout [3]. The affected code is in /tee/tee/tee_svc_cryp.c and /tee/tee/tee_obj.c, specifically the tee_obj_alloc and tee_obj_free functions [3].

Exploitation

An attacker needs to have a trusted application running in the TEE and must first disturb the heap layout, for example by calling TEE_AllocateOperation and TEE_Realloc with a large size [3]. Then, invoking TEE_AllocateOperation again triggers the vulnerable code path. The calloc function in tee_obj_alloc does not return a buffer with all bits zero as expected when the heap is disturbed, causing free(o->attr) to free an invalid pointer [3].

Impact

Successful exploitation crashes the TEE kernel, leading to a Denial of Service (DoS) [3]. The entire trusted execution environment becomes unavailable until the system is restarted.

Mitigation

As of the available references, no patched version has been released for this vulnerability, which affects mTower through v0.3.0 [1][2][3]. The issue is tracked in the mTower GitHub repository (issue #83). Users should monitor the project for an official fix and limit trust in applications running within the TEE to reduce risk [3].

AI Insight generated on May 27, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

3

News mentions

0

No linked articles in our index yet.