dbcve.org
AndroidOperating system · Google

CVE-2022-26097

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_unknown_property 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_unknown_property function of the libsimba library allows a remote attacker to trigger an out-of-bounds write, potentially leading to memory corruption and arbitrary code execution. This critical flaw exists in versions prior to the SMR Apr-2022 Release 1.

MitigationUpdate libsimba library to SMR Apr-2022 Release 1 or later to patch the vulnerability. Review and test all code paths that utilize the parser_unknown_property function to ensure the update does not introduce regressions.

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. Check Android version
    Navigate to Settings > About Phone > Android version or run 'getprop ro.build.version.release' via ADB shell
    Affected if Device is running Android 10.0, 11.0, or 12.0 - these are the affected version ranges listed in the CVE
  2. Locate libsimba library on the device
    Run 'find /system -name libsimba*' or 'find /data -name libsimba*' via ADB shell to locate the library file
    Affected if The libsimba library is present on the device, indicating the vulnerable component is installed
  3. Check libsimba library version
    If the library is found, run 'strings <path_to_libsimba> | grep -i version' or use a tool like binwalk to extract version strings from the binary
    Affected if Library version is present but earlier than SMR Apr-2022 Release 1 - the CVE states versions prior to this release are affected
  4. Verify parser_unknown_property function exists
    Run 'strings <path_to_libsimba> | grep parser_unknown_property' via ADB to confirm the vulnerable function is present in the library
    Affected if The parser_unknown_property function symbol is found in the library - this is the specific function with the null pointer dereference flaw
  5. Identify applications using libsimba
    Check installed apps that may bundle libsimba by searching APK files: 'find /data/app -name *.apk -exec unzip -l {} \; | grep -i libsimba' via ADB shell
    Affected if Any application on the device bundles or uses the libsimba library, making the vulnerability reachable through that application

A device is affected if it runs Android 10.0, 11.0, or 12.0 AND has the libsimba library present with the parser_unknown_property function at a version prior to the SMR Apr-2022 Release 1 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

Update libsimba library to SMR Apr-2022 Release 1 or later to patch the vulnerability. Review and test all code paths that utilize the parser_unknown_property function to ensure the update does not introduce regressions.

Recommended fix High confidence

SMR Apr-2022 Release 1

  1. Check your Samsung device model and current Android/SMR version in Settings > About Phone
  2. Navigate to Settings > Software Update and tap 'Download and install' to check for available updates
  3. Ensure the device updates to SMR Apr-2022 Release 1 or later which contains the libsimba library fix
  4. Verify the patch was applied by confirming the SMR version in Settings > About Phone > Software information > SMR (should show Apr-2022 or later)

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing8.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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