dbcve.org
AndroidOperating system · Google

CVE-2022-26430

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

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

Out of bounds write vulnerability in the mailbox component caused by type confusion, allowing local privilege escalation from System execution privileges. No user interaction required for exploitation.

MitigationApply vendor patch ALPS07032521 to address the type confusion vulnerability leading to out of bounds write in the mailbox component.

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= 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 or product
    Determine if the system is running Google Android or Yoctoproject Yocto
    Affected if The system is neither Android nor Yocto (different products may have similar vulnerabilities but this CVE is specific to these)
  2. Check Android version
    On Android, go to Settings > About Phone > Android version or run 'getprop ro.build.version.release' via ADB
    Affected if Android version is 11.0 or 12.0 exactly (the affected versions listed)
  3. Check Yocto version
    On Yocto, check the OS release file or run 'cat /etc/os-release' or check the build configuration
    Affected if Yocto version is 3.1 or 3.3 exactly (the affected versions listed)
  4. Verify the mailbox component is present
    Check for the presence of the mailbox component/service in the system. This is typically a kernel-level or middleware component. On Android, check /proc/mailbox or look for mailbox-related kernel modules. On Yocto, check for mailbox-related processes or kernel configuration options.
    Affected if The mailbox component is present and running (vulnerability exists in this specific component)
  5. Confirm privilege context
    Determine if the system runs services or processes with System-level privileges. On Android, most system services run at this level. Check running processes with 'ps -A' and look for those with system or root UID.
    Affected if Processes are running with System privileges (exploitation requires escalation from System privileges per the CVE description)

The system is affected if it runs Google Android version 11.0 or 12.0, or Yocto version 3.1 or 3.3, and has the mailbox component present and accessible from System privilege context.

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 ALPS07032521 to address the type confusion vulnerability leading to out of bounds write in the mailbox component.

Recommended fix Moderate confidence

Android: Any Android security update incorporating MediaTek patch ALPS07032521 (check with OEM for specific Android 12L/13 version); Yocto: Updated BSP from vendor including the MediaTek mailbox driver fix

  1. 1. Contact your device/board manufacturer (OEM/SoM vendor) to request the MediaTek patch ALPS07032521 for the mailbox driver vulnerability.
  2. 2. For Android devices: Ensure the device receives the latest Android Security Patch Level (SPL) update from your device OEM that includes the MediaTek fix.
  3. 3. For Yocto-based systems: Apply kernel and driver updates from your Yocto build's BSP (Board Support Package) vendor that incorporate the MediaTek security fix.
  4. 4. Verify the patch has been applied by checking the kernel version or security patch date after the update.
  5. 5. If no vendor update is available, consider applying the upstream MediaTek kernel patch ALPS07032521 directly to your custom kernel build if you maintain one.
Caveat Standard Android/Yocto update risks apply - test updates in non-production environment first; custom kernel builds may require additional integration work

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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