CVE-2022-26448
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 apusys, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07063849; Issue ID: ALPS07063849.
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 confidenceCVE-2022-26448 is an out-of-bounds write vulnerability in apusys, the AI Processing Unit subsystem on MediaTek chipset devices. The vulnerability stems from a missing bounds check that allows a System-level process to write beyond allocated memory boundaries, leading to local privilege escalation. No user interaction is required for exploitation.
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.0CVSS 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.
-
Check Android versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if The version is 11.0 or 12.0 exactly (not 11.0+ or 12.0+) - other versions are not affected by this specific CVE
-
Verify MediaTek chipsetRun 'getprop ro.hardware' or check /proc/cpuinfo via ADB shell; MediaTek devices typically show 'mt' followed by model number (e.g., mt6885, mt6785)Affected if The device does not use a MediaTek chipset - this vulnerability only affects MediaTek SoCs
-
Check firmware patch levelRun 'getprop ro.build.version.security_patch' via ADB to see the security patch date; compare against the vendor patch ALPS07063849Affected if The security patch level is earlier than the patch date for ALPS07063849, indicating the fix has not been applied
-
Verify apusys driver versionCheck /sys/class/misc/apusys/ or /dev/apusys* entries if accessible, or look for 'apusys' in kernel messages via 'dmesg | grep apusys'Affected if The apusys driver version cannot be verified as patched, or the driver is present and the device meets the other affected criteria
A device is affected if it runs Android 11.0 or 12.0, uses a MediaTek chipset, and lacks the ALPS07063849 firmware patch.
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 ALPS07063849 through a firmware update from the device manufacturer; affected users should ensure their devices run the latest system/firmware version.
Android Security Patch Level 2022-03-01 or later (containing ALPS07063849)
- 1. Navigate to Settings > System > System Update on the affected Android device
- 2. Check for and install any available Android security updates
- 3. Verify the device has the latest Android Security Patch Level installed
- 4. Confirm the patch ALPS07063849 is included in the installed update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26448 — 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-26448 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