In TrustZone access control policy may potentially be bypassed in all Android releases from CAF using the Linux kernel due to improper input validation an integer overflow vulnerability leading to a buffer overflow could potentially occur and a buffer over-read vulnerability could potentially occur.
CVE-2016-10239
HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-17. NVD baseline CVSS 7.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.8Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(medium)
- EPSS
- 46.9%
- KEV
- Not listed
Published
May 16, 2017
Last Modified
May 13, 2026
References (6)
- security@androidhttp://www.securityfocus.com/bid/97334
- security@androidhttp://www.securitytracker.com/id/1038201
- security@androidhttps://source.android.com/security/bulletin/2017-04-01
- af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/97334
- af854a3a-2127-422b-91ae-364da2661108http://www.securitytracker.com/id/1038201
- af854a3a-2127-422b-91ae-364da2661108https://source.android.com/security/bulletin/2017-04-01
Frequently asked(5)
What is CVE-2016-10239?
CVE-2016-10239 is a high vulnerability published on May 16, 2017. In TrustZone access control policy may potentially be bypassed in all Android releases from CAF using the Linux kernel due to improper input validation an integer overflow vulnerability leading to a buffer overflow could potentially occur and a buffer over-read vulnerability could potentially occur.
When was CVE-2016-10239 disclosed?
CVE-2016-10239 was first published in the National Vulnerability Database on May 16, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-10239 actively exploited?
CVE-2016-10239 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 46.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-10239?
CVE-2016-10239 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2016-10239?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-10239, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2016-10239
Is Your Infrastructure Affected by CVE-2016-10239?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.