CVE-2018-7992
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 · uneditedMdapt Driver of Huawei MediaPad M3 BTV-W09C128B353CUSTC128D001; Mate 9 Pro versions earlier than 8.0.0.356(C00); P10 Plus versions earlier than 8.0.0.357(C00) has a buffer overflow vulnerability. The driver does not sufficiently validate the input, an attacker could trick the user to install a malicious application which would send crafted parameters to the driver. Successful exploit could cause a denial of service condition.
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 confidenceBuffer overflow vulnerability in the Mdapt kernel driver on Huawei MediaPad M3, Mate 9 Pro, and P10 Plus devices. The driver fails to properly validate input parameters, allowing a malicious application to send crafted data that overflows a buffer, resulting in denial of service.
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= btv-w09c128b353custc128d001< 8.0.0.356\(c00\)< 8.0.0.357\(c00\)< 8.0.0.356\(c00\)CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 your device modelCheck the device settings or system information to confirm the exact model. Look for MediaPad M3, Mate 9 Pro, P10 Plus, or Mate 9.Affected if The device is NOT one of these four models, then it is not affected by this specific CVE.
-
Check the firmware version on MediaPad M3Go to Settings > About Phone > Build Number or use adb shell getprop ro.build.display.id to retrieve the firmware build. Compare it against btv-w09c128b353custc128d001.Affected if The firmware exactly matches btv-w09c128b353custc128d001, indicating the vulnerable version.
-
Check the firmware version on Mate 9 Pro or Mate 9Go to Settings > About Phone > Build Number or use adb shell getprop ro.build.display.id. Look for the version number format such as 8.0.0.xxx(c00).Affected if The firmware version is lower than 8.0.0.356(c00), meaning the device is on a vulnerable build.
-
Check the firmware version on P10 PlusGo to Settings > About Phone > Build Number or use adb shell getprop ro.build.display.id. Look for the version number format such as 8.0.0.xxx(c00).Affected if The firmware version is lower than 8.0.0.357(c00), meaning the device is on a vulnerable build.
A device is affected if it is a Huawei MediaPad M3 (firmware btv-w09c128b353custc128d001), Mate 9 Pro, Mate 9 (firmware below 8.0.0.356(c00)), or P10 Plus (firmware below 8.0.0.357(c00)) and the Mdapt kernel driver is present and accessible.
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 data8.0.0.3568.0.0.357
Update affected devices to the patched firmware versions (8.0.0.356 for Mate 9 Pro, 8.0.0.357 for P10 Plus) and avoid installing applications from untrusted sources to prevent exploitation.
- Consultation4.0 h
- Implementation2.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7992 — 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-2018-7992 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