dbcve.org
AndroidOperating system · Google

CVE-2022-21750

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 WLAN driver, 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: ALPS06521283; Issue ID: ALPS06521283.

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

This is a driver-level vulnerability in WLAN (wireless LAN) firmware where a missing bounds check allows an out-of-bounds write operation. The flaw enables local privilege escalation to System level without requiring user interaction, indicating the attacker can directly trigger the vulnerable code path.

MitigationApply the vendor patch ALPS06521283 to the WLAN driver firmware. As this is a driver-level fix requiring System privileges for exploitation, prioritize patching systems with elevated network exposure.

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. Confirm Android version
    Check the installed Android version on the device (Settings > About Phone > Android version)
    Affected if The version is exactly 11.0 or 12.0 (the only affected versions listed)
  2. Identify WLAN firmware version
    Retrieve the WLAN driver firmware version from the device (typically via dmesg, /proc/version, or vendor-specific diagnostic tools)
    Affected if The WLAN firmware version does not include the patch identifier ALPS06521283 or cannot be verified as patched
  3. Verify WLAN driver module status
    Check if the WLAN driver module is loaded and active on the system (via lsmod, kernel module listings, or system diagnostic interfaces)
    Affected if The WLAN driver module is present and operational, making the vulnerable code path accessible
  4. Assess local access vector
    Determine if untrusted local code execution is possible on the device (via installed applications, ADB access, or debugging interfaces)
    Affected if Local processes can interact with the WLAN driver, allowing trigger of the out-of-bounds write without user interaction

The device is affected if it runs Android 11.0 or 12.0 AND uses a WLAN driver firmware that lacks patch ALPS06521283, enabling local privilege escalation via the vulnerable driver code path.

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 the vendor patch ALPS06521283 to the WLAN driver firmware. As this is a driver-level fix requiring System privileges for exploitation, prioritize patching systems with elevated network exposure.

Recommended fix Moderate confidence

Android Security Bulletin February 2022 or later (containing MediaTek patch ALPS06521283)

  1. Check if your device has received the February 2022 Android Security Bulletin update or later (which includes Patch ID ALPS06521283)
  2. Verify your device's current Android Security Patch Level in Settings > About Phone > Security Patch Level
  3. If no update is available from your device OEM, contact your device manufacturer or MediaTek for the specific firmware update containing patch ALPS06521283
  4. Apply the security update through your device's standard system update mechanism
  5. Confirm the update was successfully applied by re-checking the Security Patch Level
Caveat Standard Android security update; no expected breaking changes for this patch

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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