CVE-2015-4421
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 · uneditedThe tzdriver module in Huawei Mate 7 (Mate7-TL10) smartphones before V100R001CHNC00B126SP03 allows local users to gain privileges or cause a denial of service (memory corruption) via an unspecified input.
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 privilege escalation vulnerability exists in the tzdriver (TrustZone driver) module on Huawei Mate 7 (Mate7-TL10) smartphones. Local attackers can exploit unspecified input handling to gain elevated privileges or trigger memory corruption leading to denial of service. The tzdriver module handles TrustZone interactions, and improper input validation allows local users to escape standard Android privilege boundaries.
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 data<= v100r001chnc00b123sp03CVSS 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
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/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.
-
Verify device model is Huawei Mate 7Check the device settings or boot screen to confirm the model number is Mate7 or Mate7-TL10. This vulnerability only affects these specific Huawei models.Affected if Device model is NOT Mate7 or Mate7-TL10 (different models are not affected)
-
Check firmware versionNavigate to Settings > About Phone on the device to view the build number or firmware version. Compare this version against the affected range.Affected if Firmware version is v100r001chnc00b123sp03 or earlier (the first 19 characters of the build number would be v100r001chnc00b123 or lower)
-
Confirm build number directlyIn Settings > About Phone > Version, locate the full build number string (often shown as 'Mate7-TL10V100R001CHNC00B123SP03' or similar). Extract the numeric portion after the model identifier.Affected if The build number contains 'b123sp03' or lower in the version string (anything up to and including b123sp03 is affected)
-
Verify tzdriver module presenceOn a rooted device, check /system/lib/modules/ or /vendor/lib/modules/ for the tzdriver.ko file, or view kernel module listings via 'lsmod' in a root shell. This driver is native to the affected firmware.Affected if Device is not rooted and you cannot verify the driver, assume affected if firmware version matches the vulnerable range
The device is affected only if it is a Huawei Mate 7 or Mate7-TL10 running firmware version v100r001chnc00b123sp03 or earlier; any device running a higher firmware build (b126sp03 or later) or a different model is not vulnerable to this CVE.
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 vendor firmware update V100R001CHNC00B126SP03 or later to the affected Huawei Mate 7 devices. This is a firmware-level patch requiring device update; no network-based controls can mitigate the local privilege escalation.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-4421 — 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-2015-4421 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