In TrustZone in all Android releases from CAF using the Linux kernel, a Time-of-Check Time-of-Use Race Condition vulnerability could potent…

published 2017-06-06 9y ago modified 2026-06-17 4mo ago also EUVD-2016-1482

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

In TrustZone in all Android releases from CAF using the Linux kernel, a Time-of-Check Time-of-Use Race Condition vulnerability could potentially exist.

Patch / fix

links 1

source.android.com/security/bulletin/2017-05-01 advisory

Is CVE-2016-10297 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

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

CVSS scores

assigned by	version	score	vector
NVD	3.0	7.0	CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD	2.0	9.3	AV:N/AC:M/Au:N/C:C/I:C/A:C

Affected products

Qualcomm, Inc. All Qualcomm products

Classification

Weakness

CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization

References

source.android.com /security/bulletin/2017-05-01
patch, vendor-advisory
securityfocus.com /bid/98241
vdb-entry, third-party-advisory

Sources

CVE List CVE-2016-10297
NVD CVE-2016-10297

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.