In TimeCheck::TimeCheckThread::threadLoop of TimeCheck.cpp, there is a possible use-after-free due to a race condition.

published 2020-06-11 6y ago modified 2026-06-17 4mo ago also EUVD-2020-1703

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

In TimeCheck::TimeCheckThread::threadLoop of TimeCheck.cpp, there is a possible use-after-free due to a race condition. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10Android ID: A-142142406

Patch / fix

links 1

source.android.com/security/bulletin/pixel/2020-06-01 advisory

Is CVE-2020-0199 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.10% chance of exploitation in the next 30 days, higher than 0% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	4.1	CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	1.9	AV:L/AC:M/Au:N/C:P/I:N/A:N

Affected products

n/a Android

Classification

Weakness

CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization
CWE-416 Use After Free

References

source.android.com /security/bulletin/pixel/2020-06-01
patch, vendor-advisory

Sources

CVE List CVE-2020-0199
NVD CVE-2020-0199

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.