CVE-2017-6294
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn Android before the 2018-06-05 security patch level, NVIDIA Tegra X1 TZ contains a possible out of bounds write due to missing bounds check which could lead to escalation of privilege from the kernel to the TZ. User interaction is not needed for exploitation. This issue is rated as high. Version: N/A. Android: A-69316825. Reference: N-CVE-2017-6294.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA missing bounds check in the NVIDIA Tegra X1 TrustZone (TZ) implementation allows an out-of-bounds write, enabling privilege escalation from the Android kernel to TrustZone. This high-severity vulnerability (CVSS 7.8) requires no user interaction and affects devices with the Tegra X1 processor that haven't received the June 2018 security patch.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the processorCheck if the device uses the NVIDIA Tegra X1 processor. On Android, this information can be found in /proc/cpuinfo or under Settings > About Phone > CPU. Look for 'Tegra' or 'X1' in the processor information.Affected if The device does not have a Tegra X1 processor, as this vulnerability specifically targets that hardware.
-
Check the Android security patch levelNavigate to Settings > About Phone > Android security patch level. This displays the month and year of the last security update installed on the device.Affected if The patch level is earlier than June 2018, meaning the device has not received the fix for this TrustZone vulnerability.
-
Verify the build fingerprint for patch dateRun 'getprop ro.build.version.security_patch' via ADB or terminal emulator. This returns the exact security patch date in YYYY-MM-DD format.Affected if The returned date is earlier than 2018-06-01, indicating the device is running an unpatched version.
-
Confirm TrustZone is accessibleThis vulnerability allows escalation from the Android kernel to TrustZone. No specific command confirms exploitation, but the presence of Tegra X1 hardware combined with an outdated patch level means the attack surface exists.Affected if The device has Tegra X1 hardware and the security patch level is before June 2018.
A device is affected if it contains an NVIDIA Tegra X1 processor and is running an Android security patch level earlier than June 2018.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the June 2018 Android security patch level or later, which includes the NVIDIA fix for this TrustZone vulnerability. Devices running older patch levels remain vulnerable and should be updated or replaced.
- Consultation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6294 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-6294 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data