dbcve.org
AndroidOperating system · Google

CVE-2022-21766

MEDIUM · 6.7 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 →
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 CCCI, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06641673; Issue ID: ALPS06641653.

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 missing bounds check in the CCCI (Centralized Component Communication Interface) driver allows an out-of-bounds write, enabling local privilege escalation from System privileges. The vulnerability requires no user interaction and affects MediaTek-based mobile devices.

MitigationApply vendor patch ALPS06641673 to the CCCI driver. This is a driver-level fix requiring kernel/baseband subsystem updates from the device OEM or MediaTek.

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= 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. Identify MediaTek chipset presence
    Check /proc/cpuinfo or use 'getprop ro.hardware' or 'cat /sys/devices/soc0/hardware' to determine if the device uses a MediaTek (MTK) SoC. The CCCI driver is specific to MediaTek platforms.
    Affected if The device does not use a MediaTek chipset - this vulnerability only affects MediaTek-based Android devices.
  2. Verify Android version
    Run 'getprop ro.build.version.release' or check Settings > About Phone > Android version. Confirm the exact version is 10.0, 11.0, or 12.0.
    Affected if The installed Android version is exactly 10.0, 11.0, or 12.0.
  3. Confirm CCCI driver is present
    Check for the presence of the CCCI driver by examining /proc/ccci or /dev/ccci, or run 'ls -la /sys/kernel/debug/ccci' if debugfs is accessible. Also check 'getprop ro.ccci' or search kernel logs with 'dmesg | grep -i ccci'.
    Affected if The CCCI driver is loaded and accessible on the device.
  4. Check vendor security patch level
    Run 'getprop ro.build.version.security_patch' to retrieve the applied security patch level. Compare this against the vendor patch ALPS06641673 which addresses this issue.
    Affected if The security patch level is earlier than the vendor patch containing ALPS06641673, or the patch has not been applied.

A device is affected if it uses a MediaTek chipset, runs Android 10.0, 11.0, or 12.0, has the CCCI driver present, and lacks the vendor-specific patch ALPS06641673.

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 ALPS06641673 to the CCCI driver. This is a driver-level fix requiring kernel/baseband subsystem updates from the device OEM or MediaTek.

Recommended fix Moderate confidence
  1. Contact your Android device OEM manufacturer for a firmware update that includes the MediaTek security patch ALPS06641673
  2. Provide the device model and build number to the OEM to verify if the patch has been applied
  3. Alternatively, check for Android system updates in Settings > System > Security Update on your device
  4. Verify the patch has been applied by confirming the Android security patch level includes the fix for CVE-2022-21766
  5. If no update is available from the OEM, consider using a device that receives timely security updates
Caveat Firmware updates from OEM may have additional changes; ensure backup before applying

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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