dbcve.org
AndroidOperating system · Google

CVE-2022-21751

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: ALPS06511132; Issue ID: ALPS06511132.

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 missing bounds check in the WLAN driver allows an out-of-bounds write vulnerability, enabling local privilege escalation from a user context to System execution privileges without requiring user interaction.

MitigationApply the vendor patch (ALPS06511132) to update the affected WLAN driver firmware or software to remediate the missing bounds check that enables the out-of-bounds write.

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

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 is 11.0
    Check the device Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell. The affected version is exactly 11.0, not a range.
    Affected if The Android version shows 11.0 (exact match)
  2. Verify WLAN hardware is present
    Check if the device has WLAN capability by looking for Wi-Fi settings, or run 'wpa_supplicant' or check for WLAN interface (e.g., wlan0) using 'ip link' or 'ifconfig' via ADB shell.
    Affected if WLAN hardware and interface are present on the device
  3. Check if WLAN driver module is loaded
    Run 'lsmod' via ADB shell to list loaded kernel modules, or check /proc/modules for WLAN-related driver modules (common names include wlan, wifi, ath, bcmdhd, wl, mwifiex).
    Affected if A WLAN driver kernel module is loaded and active
  4. Verify vendor patch ALPS06511132 status
    Check build fingerprint or security patch level via Settings > About Phone > Build number, or run 'getprop ro.build.version.security_patch' and 'getprop ro.vendor.build.fingerprint' via ADB shell. Compare against the patch date.
    Affected if The device has not received vendor patch ALPS06511132, leaving the vulnerable WLAN driver in place

A device is affected if it runs Android exactly version 11.0, has active WLAN hardware/driver, and lacks the vendor patch ALPS06511132.

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 (ALPS06511132) to update the affected WLAN driver firmware or software to remediate the missing bounds check that enables the out-of-bounds write.

Recommended fix Moderate confidence

Apply Android system update containing MediaTek patch ALPS06511132

  1. Check for system updates on the affected Android 11.0 device by navigating to Settings > System > Software Update or Settings > About Phone > System Update
  2. Apply any available system updates which may include the MediaTek WLAN driver patch ALPS06511132
  3. If no update is available, contact the device manufacturer (OEM) or carrier to confirm when the patch will be delivered
  4. Verify the device has the latest security patch level after updating
Caveat None expected; patch updates are backward compatible

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

Fix this in Android Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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