dbcve.org
AndroidOperating system · Google

CVE-2022-26466

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 audio ipi, there is a possible out of bounds write due to an integer overflow. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06558777; Issue ID: ALPS06558777.

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

In MediaTek's audio IPI (Inter-Processor Interrupt) driver, an integer overflow vulnerability exists that can lead to an out-of-bounds memory write. This could allow a local attacker with System-level execution privileges to escalate privileges further.

MitigationApply vendor patch ALPS06558777; until then, restrict local access to the audio subsystem and monitor for anomalous audio driver behavior.

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

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 if the device uses a MediaTek SoC
    Check /proc/cpuinfo or dmesg for 'MediaTek' or 'MT' in the processor/hardware information
    Affected if The system does not have MediaTek hardware, the driver vulnerability does not apply
  2. Verify the audio IPI driver is present
    Look for the audio IPI driver module in /proc/modules, lsmod output, or kernel config (CONFIG_MTK_AUDIO_IPI or similar)
    Affected if The audio IPI driver is not loaded or compiled into the kernel, the vulnerability cannot be exploited
  3. Confirm the OS version matches affected releases
    Check Android build number (Settings > About Phone > Build Number) for 11.0 or 12.0; on Yocto, run 'cat /etc/os-release' and check the VERSION_ID
    Affected if The installed OS version is NOT Android 11.0, Android 12.0, or Yocto 3.1, the specific vulnerability variant may not be present
  4. Check for vendor security patches
    On Android, go to Settings > Security > Security patch level; on Yocto, review installed kernel-package version against MediaTek ALPS06558777 patch date
    Affected if The security patch level is earlier than the vendor fix for this CVE, the vulnerability remains unpatched

The environment is affected if it runs on MediaTek hardware with the audio IPI driver enabled, uses Android 11.0/12.0 or Yocto 3.1, and lacks the ALPS06558777 vendor patch.

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 ALPS06558777; until then, restrict local access to the audio subsystem and monitor for anomalous audio driver behavior.

Recommended fix Moderate confidence

Android: March 2022 Security Patch Level or later; Yocto: Check vendor for updated kernel/firmware containing ALPS06558777

  1. 1. Identify the MediaTek SoC model in the affected device by checking /proc/cpuinfo or vendor documentation
  2. 2. Contact the device OEM/vendor to confirm they have applied the MediaTek patch ALPS06558777
  3. 3. For Android devices: Verify the Android Security Patch Level (SPL) in Settings > About Phone > Build Number - this vulnerability was addressed in the March 2022 Android Security Bulletin or later
  4. 4. For Yocto systems: Check for kernel/firmware updates from the board vendor or Meta-MediaTek layer that include the fix for ALPS06558777
  5. 5. Apply the vendor-provided security update containing the patched MediaTek audio driver
Caveat Security-only patch; no expected breaking changes but verify on test device before broad deployment

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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