dbcve.org
AndroidOperating system · Google

CVE-2022-32632

MEDIUM · 6.7 CVSS v3.1 Published 2022-12-05
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 Wi-Fi, there is a possible out of bounds write due to improper input validation. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07441630; Issue ID: ALPS07441630.

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 vulnerability in the Wi-Fi component allows an out-of-bounds write due to improper input validation, enabling local privilege escalation to System execution privileges without user interaction.

MitigationApply vendor patch ALPS07441630; until patched, consider disabling Wi-Fi as a temporary mitigation to reduce attack surface.

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= 13.0
YoctoOperating system
Affected:= 3.1= 3.3

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 the operating system and version
    On Android: Go to Settings > About Phone > Android version. On Yocto: Check /etc/os-release or run 'cat /etc/version'
    Affected if The device runs Google Android versions 11.0, 12.0, or 13.0, or Yoctoproject Yocto versions 3.1 or 3.3
  2. Confirm Wi-Fi component is present and enabled
    On Android: Check Settings > Network & Internet > Wi-Fi is toggled on. On embedded systems: Check if Wi-Fi driver module is loaded via 'lsmod' or if Wi-Fi interface exists via 'ip link show'
    Affected if Wi-Fi hardware is present and the Wi-Fi software stack is active on the device
  3. Check if vendor patch ALPS07441630 has been applied
    On Android: Check system security patch level in Settings > About Phone > Security patch level. On Yocto: Query the installed package database for the Wi-Fi component patch, e.g., 'rpm -qa | grep -i wifi' and review changelogs
    Affected if The system security patch level is earlier than the vendor patch date, or the specific patch ALPS07441630 is not listed in installed updates

The device is affected if it runs Android 11.0/12.0/13.0 or Yocto 3.1/3.3, has Wi-Fi enabled, and lacks vendor patch ALPS07441630.

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 ALPS07441630; until patched, consider disabling Wi-Fi as a temporary mitigation to reduce attack surface.

Recommended fix Moderate confidence
  1. 1. Contact the MediaTek device OEM/vendor to request the security update containing patch ALPS07441630 for this vulnerability.
  2. 2. For Android devices, check for and apply the latest Android Security Patch Level (SPL) that incorporates the MediaTek Wi-Fi driver fix. This CVE may be listed in the Android Security Bulletin for the month the fix was released.
  3. 3. For Yocto systems, update the Linux kernel package to a version that includes the MediaTek Wi-Fi driver security fix. Check Yocto security notices for CVE-2022-32632 for the specific package version.
  4. 4. Verify the patch has been applied by checking the Wi-Fi driver version or reviewing the system security patch level.
  5. 5. Reboot the device after applying the update to ensure the patched Wi-Fi driver is loaded.

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