dbcve.org
AndroidOperating system · Google

CVE-2022-26094

CRITICAL · 9.8 CVSS v3.1 Published 2022-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Null pointer dereference vulnerability in parser_auxC function in libsimba library prior to SMR Apr-2022 Release 1 allows out of bounds write by remote attacker.

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 null pointer dereference in the parser_auxC function of the libsimba library prior to the SMR Apr-2022 Release enables a remote attacker to perform an out-of-bounds write, potentially leading to arbitrary code execution. The vulnerability has a critical CVSS score of 9.8, indicating severe risk to affected systems.

MitigationUpdate the libsimba library to SMR Apr-2022 Release 1 or later to patch the vulnerability. Conduct a thorough inventory of all systems and applications using this library to ensure complete coverage.

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:= 10.0= 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 Android version
    Check the device or application target Android version in system settings or build configuration
    Affected if Android version equals 10.0, 11.0, or 12.0
  2. Locate libsimba library
    Search the system or application package for the presence of libsimba library files (typically named libsimba.so or similar)
    Affected if libsimba library is present on the device or bundled in the application
  3. Determine libsimba version
    Inspect the library file metadata, version resources, or check the build manifest for the libsimba version string
    Affected if libsimba version is prior to SMR Apr-2022 Release 1 (version information missing, older, or unpatched)
  4. Verify parser functionality is used
    Review application code or network traffic to determine if the parser_auxC function is invoked for processing external input
    Affected if The application uses libsimba parser functions to process untrusted data

The environment is affected if running Android 10.0, 11.0, or 12.0 with a libsimba library version prior to SMR Apr-2022 Release 1 that utilizes the vulnerable parser function.

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

Update the libsimba library to SMR Apr-2022 Release 1 or later to patch the vulnerability. Conduct a thorough inventory of all systems and applications using this library to ensure complete coverage.

Recommended fix High confidence

SMR Apr-2022 Release 1 (or later)

  1. Check your Samsung device model and carrier/region variant
  2. Navigate to Settings > Software Update on your Samsung device
  3. Ensure you are connected to Wi-Fi and have sufficient battery
  4. Tap 'Download and install' to check for available updates
  5. If available, download and install the SMR (Samsung Maintenance Release) April-2022 update or later
  6. After installation, verify the patch level in Settings > About phone > Software information shows the April 2022 security patch or later
  7. Alternatively, contact your device manufacturer or carrier for the specific security update containing the libsimba library fix
Caveat Standard firmware update risks apply - ensure device is adequately charged and backed up before applying

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

Fix this in Android Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,520
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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