dbcve.org
AndroidOperating system · Google

CVE-2022-21776

MEDIUM · 6.4 CVSS v3.1 Published 2022-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
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 MDP, there is a possible use after free due to a race condition. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06545450; Issue ID: ALPS06545450.

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 use-after-free vulnerability exists in MediaTek's MDP (Mobile Display Processor) component due to a race condition. The flaw allows a local attacker with System-level privileges to potentially escalate privileges by exploiting the race condition to achieve use-after-free, leading to arbitrary code execution in the kernel context.

MitigationApply vendor patch ALPS06545450 to affected MediaTek-based devices. Given the System-level prerequisite and kernel context of the vulnerability, prioritize patching on all supported devices in your fleet.

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:= 11.0= 12.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
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:H/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 11.0 or 12.0
    Check the device settings under Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if Android version equals 11.0 or 12.0 exactly
  2. Confirm MediaTek SoC is present
    Check the processor information via 'getprop ro.hardware' or 'cat /proc/cpuinfo' to identify MediaTek hardware, as this vulnerability is specific to MediaTek's MDP component
    Affected if Device uses a MediaTek-based SoC
  3. Verify MDP driver is loaded
    Check for MDP-related kernel modules or device nodes: look for 'mdp' entries in /proc/modules, /sys/module/, or check 'dmesg' for MDP driver initialization messages
    Affected if MDP (Mobile Display Processor) driver is present and loaded on the device
  4. Check for patch ALPS06545450 presence
    Query the system build fingerprint or security patch level via 'getprop ro.build.version.security_patch' or check MediaTek-specific patch metadata if available through vendor channels
    Affected if Security patch level is earlier than the one containing ALPS06545450, or patch is not applied

A device is affected if it runs Android 11.0 or 12.0 on MediaTek hardware with the MDP driver loaded and is missing the ALPS06545450 vendor patch.

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 ALPS06545450 to affected MediaTek-based devices. Given the System-level prerequisite and kernel context of the vulnerability, prioritize patching on all supported devices in your fleet.

Recommended fix Moderate confidence

Android Security Patch Level incorporating MediaTek patch ALPS06545450 (typically January 2022 or later security bulletin)

  1. 1. Check if your Android device manufacturer (OEM) has released a security update that includes MediaTek patch ALPS06545450
  2. 2. Go to Settings > System > System Update (or Settings > About Phone > Software Update) on your Android device
  3. 3. Check for and install any available security updates
  4. 4. If no update is available, contact your device manufacturer or carrier to request the security patch
Caveat Security updates are generally safe to apply; OEM updates may include other changes but are recommended for security

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

Fix this in Android Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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