dbcve.org
Berkeley Al20 FirmwareOperating system · Huawei

CVE-2018-7899

MEDIUM · 5.5 CVSS v3.0 Published 2018-04-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 · unedited
The Mali Driver of Huawei Berkeley-AL20 and Berkeley-BD smart phones with software Berkeley-AL20 8.0.0.105(C00), 8.0.0.111(C00), 8.0.0.112D(C00), 8.0.0.116(C00), 8.0.0.119(C00), 8.0.0.119D(C00), 8.0.0.122(C00), 8.0.0.132(C00), 8.0.0.132D(C00), 8.0.0.142(C00), 8.0.0.151(C00), Berkeley-BD 1.0.0.21, 1.0.0.22, 1.0.0.23, 1.0.0.24, 1.0.0.26, 1.0.0.29 has a double free vulnerability. An attacker can trick a user to install a malicious application and exploit this vulnerability when in the exception handling process. Successful exploitation may cause system reboot.

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 confidence

A double free vulnerability exists in the Mali GPU driver of Huawei Berkeley-AL20 and Berkeley-BD smartphones. An attacker tricks a user into installing a malicious application which triggers the double free condition during the exception handling process, potentially causing a system reboot (denial of service).

MitigationSince this is a kernel-level driver vulnerability in mobile firmware, remediation requires applying vendor-supplied security patches. Organizations should inventory affected devices, monitor for vendor updates, and consider restricting application installation to trusted sources until patches are available.

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
Berkeley Al20 FirmwareOperating system
Affected:= 8.0.0.105\(c00\)= 8.0.0.111\(c00\)= 8.0.0.112d\(c00\)= 8.0.0.116\(c00\)= 8.0.0.119\(c00\)= 8.0.0.119d\(c00\)= 8.0.0.122\(c00\)= 8.0.0.132\(c00\)= 8.0.0.132d\(c00\)= 8.0.0.142\(c00\)= 8.0.0.151\(c00\)
Berkeley Bd FirmwareOperating system
Affected:= 1.0.0.21= 1.0.0.22= 1.0.0.23= 1.0.0.24= 1.0.0.26= 1.0.0.29

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Check the device model number in Settings > About Phone. Confirm it is either Huawei Berkeley-AL20 or Berkeley-BD.
    Affected if Device model is not Berkeley-AL20 or Berkeley-BD, then not affected.
  2. Check firmware version on Berkeley-AL20
    Navigate to Settings > About Phone > Version. Compare the displayed firmware version against the list: 8.0.0.105(c00), 8.0.0.111(c00), 8.0.0.112d(c00), 8.0.0.116(c00), 8.0.0.119(c00), 8.0.0.119d(c00), 8.0.0.122(c00), 8.0.0.132(c00), 8.0.0.132d(c00), 8.0.0.142(c00), 8.0.0.151(c00).
    Affected if Firmware version matches one of the listed versions, then device is affected.
  3. Check firmware version on Berkeley-BD
    Navigate to Settings > About Phone > Version. Compare the displayed firmware version against the list: 1.0.0.21, 1.0.0.22, 1.0.0.23, 1.0.0.24, 1.0.0.26, 1.0.0.29.
    Affected if Firmware version matches one of the listed versions, then device is affected.
  4. Verify Mali GPU driver presence
    The Mali GPU driver is required for this vulnerability to be exploitable. Confirm the device uses a Mali GPU by reviewing kernel logs or using a system information app that displays GPU details.
    Affected if Device does not have a Mali GPU driver, then not affected.

The device is affected only if it is a Huawei Berkeley-AL20 or Berkeley-BD model running one of the specific firmware versions listed, and the device uses a Mali GPU driver.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since this is a kernel-level driver vulnerability in mobile firmware, remediation requires applying vendor-supplied security patches. Organizations should inventory affected devices, monitor for vendor updates, and consider restricting application installation to trusted sources until patches are available.

Fix this in Berkeley Al20 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-7899 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-7899 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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