dbcve.org
AndroidOperating system · Google

CVE-2022-21758

MEDIUM · 6.7 CVSS v3.1 Published 2022-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/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 ccu, there is a possible memory corruption due to a double free. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06439600; Issue ID: ALPS06439600.

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 double-free vulnerability in the ccu component (a driver or system service) allows memory corruption, potentially enabling local privilege escalation from System privileges. The vulnerability stems from improper memory management where memory is freed twice, leading to use-after-free conditions that could be exploited for privilege escalation.

MitigationApply patch ALPS06439600 to the ccu component in the firmware. This is a firmware-level fix requiring integration of the vendor patch into the system image.

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

CVSS:3.1/AV:L/AC:L/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
    Check the device settings or use 'getprop ro.build.version.release' to confirm the installed Android version
    Affected if The version is exactly 11.0 or 12.0 - other versions are not affected by this CVE
  2. Identify ccu component presence
    Search for the ccu driver or service file on the system. Common locations include /system/lib/, /vendor/lib/, /dev/, or check process list for ccu-related entries using 'ps -A | grep -i ccu'
    Affected if The ccu component is present and running on the device - if ccu does not exist, the device is not affected
  3. Check ccu service status
    Examine if the ccu service is actively running as a system service. Use 'getprop' or check /sys/ or /proc/ for ccu-related entries
    Affected if The ccu service is enabled and running - the vulnerability only applies when the ccu component is active
  4. Confirm privilege context
    Verify the Android device is running with System-level privileges accessible to the attacker context - this is implied by default on Android but the exploitation targets System privilege escalation
    Affected if The device runs standard Android with System-level processes - the flaw enables escalation from System to higher privileges

A device is affected only if it runs Android 11.0 or 12.0 AND has the ccu component present and enabled - the double-free only occurs within the ccu driver/service context.

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 patch ALPS06439600 to the ccu component in the firmware. This is a firmware-level fix requiring integration of the vendor patch into the system image.

Recommended fix Moderate confidence
  1. Check your device's Android Security Patch Level in Settings > About Phone > Security Patch Level
  2. Ensure your device has the January 2022 or later Android Security Update installed
  3. If the update is not available, contact your device manufacturer (OEM) for the ALPS06439600 patch
  4. Alternatively, wait for your device manufacturer to push the monthly security update containing this fix
  5. For developers: The fix is in MediaTek's ALPS06439600 patch - ensure any custom ROMs or MediaTek camera drivers include this patch

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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