dbcve.org
AndroidOperating system · Google

CVE-2022-20026

HIGH · 7.8 CVSS v3.1 Published 2022-02-09
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 Bluetooth, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06126827; Issue ID: ALPS06126827.

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 MediaTek Bluetooth stack (ALPS) allows an out-of-bounds write, leading to local privilege escalation without requiring user interaction or additional execution privileges. The vulnerability stems from insufficient input validation in Bluetooth processing code.

MitigationApply vendor patch ALPS06126827 to affected MediaTek device firmware. Until the patch is available, monitor for unauthorized Bluetooth access and restrict Bluetooth usage to trusted devices.

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:= 8.1= 9.0= 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
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. Confirm device uses a MediaTek chipset
    Check device information in Settings > About Phone > Model/Hardware or run 'getprop ro.hardware' via ADB. MediaTek devices typically show 'mtk' or MediaTek in the hardware/processor details.
    Affected if The device does not have a MediaTek chipset - this vulnerability only affects MediaTek Bluetooth stack (ALPS), not Qualcomm or other implementations.
  2. Check Android OS version
    Navigate to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB.
    Affected if The version is NOT 8.1, 9.0, 10.0, 11.0, or 12.0 - only these specific Android versions listed in the affected products are vulnerable.
  3. Verify MediaTek Bluetooth firmware/patch level
    Check the MediaTek patch level in Settings > About Phone > Build number, or obtain via 'getprop ro.build.version.mtk' and 'getprop ro.mtk.version.patch' via ADB.
    Affected if The patch level is earlier than ALPS06126827 - the vulnerability exists in the MediaTek Bluetooth stack when this specific vendor patch is not applied.
  4. Confirm Bluetooth hardware component exists
    Verify Bluetooth is present by checking 'getprop ro.bluetooth' via ADB or confirming Bluetooth in Settings.
    Affected if The device lacks Bluetooth hardware entirely - while unlikely for affected MediaTek Android devices, the vulnerability only applies to systems with the MediaTek Bluetooth stack.

A device is affected if it uses a MediaTek chipset, runs Android 8.1 through 12.0, and has not received the ALPS06126827 patch in its MediaTek Bluetooth firmware.

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 ALPS06126827 to affected MediaTek device firmware. Until the patch is available, monitor for unauthorized Bluetooth access and restrict Bluetooth usage to trusted devices.

Recommended fix High confidence

Android Security Patch Level (latest available from OEM, containing MediaTek patch ALPS06126827)

  1. Check the current Android Security Patch Level on the device by going to Settings > About Phone > Security Patch Level
  2. Contact the device manufacturer (OEM) to request the security update containing MediaTek patch ALPS06126827
  3. Apply the latest available Android Security Patch Level update for your device
  4. If the OEM does not provide an update, consider upgrading to a device model with active security support
Caveat OEM security updates are device-specific; not all devices receive updates; some may require manual firmware flash

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-20026 — 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-20026 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