dbcve.org
AndroidOperating system · Google

CVE-2022-26460

MEDIUM · 6.7 CVSS v3.1 Published 2022-09-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 vow, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07032590; Issue ID: ALPS07032590.

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 bounds check vulnerability in the vow (Voice Wake-up) component of MediaTek's ALPS firmware allows an attacker with System execution privileges to write beyond allocated buffer boundaries. The flaw exists in the bounds checking logic, enabling local privilege escalation without user interaction.

MitigationApply the MediaTek firmware patch ALPS07032590 through the device vendor's security update channel; this is a low-level firmware fix requiring system-level execution for installation.

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. Identify the Android version
    Go to Settings > About Phone > Android version (or run 'getprop ro.build.version.release' via ADB)
    Affected if The version is exactly 11.0 or 12.0 (not 11.0.x or 12.0.x variants, but specifically 11.0 and 12.0)
  2. Confirm MediaTek chipset presence
    Run 'getprop ro.hardware' or 'getprop ro.chipname' via ADB, or check in Settings > About Phone > Chipset info
    Affected if The device uses a MediaTek (MTK) processor; this vulnerability is specific to MediaTek ALPS firmware
  3. Verify the vow voice wake-up component
    Check for the vow service in /system/vendor/lib/ or /vendor/lib/ (vow.*.so files), or run 'getprop | grep vow' via ADB
    Affected if The vow (Voice Wake-up) module is present and loaded on the device
  4. Confirm System execution privileges
    This check requires already having elevated privileges - the vulnerability requires System-level access to exploit
    Affected if The attacker already has System-level execution privileges on the compromised device

The device is affected only if it runs Android exactly version 11.0 or 12.0, uses a MediaTek chipset with the vow component present, and the attacker already possesses System execution privileges.

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 MediaTek firmware patch ALPS07032590 through the device vendor's security update channel; this is a low-level firmware fix requiring system-level execution for installation.

Recommended fix High confidence

Android Security Patch Level containing the ALPS07032590 fix (typically included in March 2022 or later MediaTek-based security updates)

  1. Check your device for system updates by going to Settings > System > Software Update (or Settings > About Phone > Software Update)
  2. Apply any available system updates from your device manufacturer
  3. Verify the security patch level after updating: go to Settings > About Phone > Android version or Security patch level
  4. If no update is available, contact your device manufacturer or carrier for the patch incorporating MediaTek patch ID ALPS07032590

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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