CVE-2022-26435
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 · uneditedIn 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: ALPS07138435; Issue ID: ALPS07138435.
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 confidenceThis is a type confusion vulnerability in the mailbox component (inter-process communication subsystem) that leads to an out-of-bounds write. It allows local privilege escalation from an arbitrary application to System execution privileges without requiring user interaction.
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= 11.0= 12.0= 3.1= 3.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Android versionOn the Android device, go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if The version is 11.0 or 12.0 exactly
-
Identify the Yocto Project versionCheck the file /etc/os-release or run 'cat /etc/yocto-release' if present, or check the kernel config for YOCTO version indicatorsAffected if The Yocto version is 3.1 or 3.3 exactly
-
Determine if the mailbox IPC component is presentCheck for the presence of the mailbox driver module by looking for files matching 'mailbox' in /sys/module/ or /lib/modules/, or check kernel config for CONFIG_MAILBOX or similar optionsAffected if The mailbox module is loaded or built into the kernel (required for the vulnerability to be exploitable)
You are affected if your Android version is 11.0 or 12.0, or your Yocto version is 3.1 or 3.3, AND the mailbox IPC component is present in your kernel.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the vendor patch (ALPS07138435) through system/ROM updates. Since this is a kernel-adjacent component, remediation typically requires updating the device firmware or kernel modules containing the mailbox driver.
Android: Latest Security Patch Level (SPL) containing MediaTek patch ALPS07138435; Yocto: Kernel version with MediaTek ALPS07138435 fix incorporated
- 1. Check the MediaTek Security Bulletin for CVE-2022-26435 to identify the specific patch release date
- 2. For Android devices: Apply the latest Android Security Patch Level (SPL) update from your device OEM that includes the MediaTek patch ALPS07138435
- 3. For Yocto systems: Update the Linux kernel package to a version that includes the fix for ALPS07138435 in the MediaTek mailbox driver
- 4. Verify the patch is applied by checking the kernel configuration or contacting the device vendor
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26435 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-26435 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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