dbcve.org
Nn Android Neural Networks DriverApplication · Arm

CVE-2023-26085

HIGH · 7.8 CVSS v3.1 Published 2023-06-29
Fix available
A fix is available. Upgrade to 23.02 or later.
See remediation →
80/100
Remediation priority · High
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
A possible out-of-bounds read and write (due to an improper length check of shared memory) was discovered in Arm NN Android-NN-Driver before 23.02.

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

An out-of-bounds read and write vulnerability exists in Arm NN Android-NN-Driver due to improper length validation when handling shared memory. This allows memory corruption through malformed shared memory operations, potentially enabling local privilege escalation or arbitrary code execution.

MitigationUpdate Arm NN Android-NN-Driver to version 23.02 or later, which contains the proper length check fixes for shared memory operations.

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
Nn Android Neural Networks DriverApplication
Affected:< 23.02

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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. Locate Arm NN Android-NN-Driver library
    Search for the driver library on the Android device, typically found in /vendor/lib/ or /system/lib/ with names containing 'android_nn' or 'arm_nn' (e.g., libandroid_nn_driver.so or similar)
    Affected if The library file exists on the device
  2. Identify the installed driver version
    Extract version metadata from the driver library using 'getprop' commands for Android properties, or use 'strings' command on the .so file to search for version strings like '23.02' or version-related metadata
    Affected if Version cannot be determined or is lower than 23.02
  3. Verify shared memory handling is in use
    Check if the Android Neural Networks API (NNAPI) is actively using the Arm NN driver by examining /sys/class/android_usb/android0/f_acm/uevent or checking NNAPI delegation status in app debug logs, or by reviewing /vendor/etc/android_armnn.ini or similar configuration files if they exist
    Affected if NNAPI is actively routing computations through Arm NN driver and driver version is below 23.02

The environment is affected if Arm NN Android-NN-Driver is present and its version is determined to be below 23.02, with shared memory operations actively in use through the NNAPI.

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
Upgrade available Upgrade to 23.02 or later
Fixed in 23.02
Interim mitigation

Update Arm NN Android-NN-Driver to version 23.02 or later, which contains the proper length check fixes for shared memory operations.

Recommended fix High confidence

23.02 or later

  1. 1. Identify the current version of Arm NN Android-NN-Driver in use by checking the build configuration or library files.
  2. 2. Obtain the fixed release version 23.02 or later from the official Arm NN repository (github.com/ARM-software/armnn) or Arm's developer portal (developer.arm.com).
  3. 3. Update the build configuration or dependency management system to reference version 23.02 or the latest stable release.
  4. 4. Rebuild the Android image or application that includes the Arm NN Android-NN-Driver.
  5. 5. Verify the update was successful by checking the driver version matches the patched release.
  6. 6. Test the Neural Networks functionality to ensure the driver operates correctly after the upgrade.
Caveat Check release notes for any API changes or breaking changes between the current version and 23.02

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

Fix this in Nn Android Neural Networks Driver Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

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