Linaro/OP-TEE OP-TEE Prior to version v3.4.0 is affected by: Boundary checks.

published 2019-07-16 7y ago modified 2026-06-17 4mo ago also EUVD-2019-2028

cvss: 9.8; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.6%; EPSS 1.6% chance of exploitation in 30 days, percentile 75%
public exploits: 0; none known

Linaro/OP-TEE OP-TEE Prior to version v3.4.0 is affected by: Boundary checks. The impact is: This could lead to corruption of any memory which the TA can access. The component is: optee_os. The fixed version is: v3.4.0.

Patch / fix

fixed in 1 links 1

trustedfirmware op-tee 3.4.0

github.com/OP-TEE/optee_os@e3adcf5 commit

Is CVE-2019-1010292 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.58% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	9.8	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	7.5	AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected products

Linaro/OP-TEE OP-TEE

Classification

Weakness

CWE-787 Out-of-bounds Write

References

github.com /OP-TEE/optee_os/commit/e3adcf566cb278444830e7badfdcc3983e334fd1
patch, third-party-advisory

Sources

CVE List CVE-2019-1010292
NVD CVE-2019-1010292

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.