dbcve.org
AndroidOperating system · Google

CVE-2021-0610

HIGH · 7.8 CVSS v3.1 Published 2021-09-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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
In memory management driver, there is a possible memory corruption due to an integer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS05403499; Issue ID: ALPS05411456.

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 · moderate confidence

A memory management driver contains an integer overflow vulnerability that allows a local attacker to corrupt memory, potentially leading to privilege escalation. The flaw requires no user interaction or additional execution privileges to exploit, making it highly dangerous for local attacks.

MitigationApply vendor patch ALPS05403499 to address the integer overflow in the memory management driver. This is typically delivered through system/firmware updates from the device vendor.

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
AndroidOperating system
Affected:= 10.0= 11.0

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/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 checks

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

  1. Verify Android version is 10.0 or 11.0
    Go to Settings > About Phone (or About Device) > Android version. Confirm the version number displayed is exactly 10.0 or 11.0. This vulnerability only affects these specific versions.
    Affected if Android version shows 10.0 or 11.0 exactly (not 10.0.x or 11.0.x variants)
  2. Check security patch level
    Go to Settings > About Phone > Security patch level. Note the date shown (for example, 'January 5, 2021' or similar). Compare this to when vendor patches became available.
    Affected if Security patch level is earlier than the vendor release date for patch ALPS05403499
  3. Identify device manufacturer and model
    Note the device make and model from Settings > About Phone. Different manufacturers deliver the Android security updates at different times based on their update schedules.
    Affected if Device is from a manufacturer that has not yet released the ALPS05403499 patch for Android 10.0 or 11.0
  4. Check kernel version if accessible
    On a rooted device or through ADB, run 'cat /proc/version' or 'uname -a' to view kernel build information. The memory management driver vulnerability exists at the kernel level.
    Affected if Kernel version corresponds to an unpatched Android 10.0 or 11.0 build

You are affected if your device runs Android version 10.0 or 11.0 exactly and has not received the vendor security patch that addresses the integer overflow in the memory management 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch ALPS05403499 to address the integer overflow in the memory management driver. This is typically delivered through system/firmware updates from the device vendor.

Recommended fix Moderate confidence

Android 12 or later (includes MediaTek ALPS05403499 fix)

  1. 1. Check if your device manufacturer has released a security patch that includes MediaTek patch ID ALPS05403499
  2. 2. If available, apply the latest security update from your device OEM
  3. 3. Alternatively, upgrade to Android 12 or later, which includes the patched MediaTek memory management driver
  4. 4. Verify the patch has been applied by checking your device security patch level in Settings > About Phone > Security Patch Level
Caveat Minor - Android 12 upgrade may introduce UI changes; verify app compatibility before deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-0610 — 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-2021-0610 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