# CVE-2023-26085: Memory corruption in n/a

> An out-of-bounds read and write in the Arm NN Android-NN-Driver allows attackers to potentially execute code or escalate privileges.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Jun 2023
- **Updated:** 27 Nov 2024
- **Also known as:** A-261701167, ASB-A-261701167, GHSA-35cf-pg5x-4f5c

## What is CVE-2023-26085?

CVE-2023-26085 is a high-severity memory corruption vulnerability in n/a, published on 29 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-787 (Out-of-bounds Write), CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2023-26085?

It affects 1 product.


Products: Arm Nn Android Neural Networks Driver.

## How do I fix CVE-2023-26085?

Apply the vendor's patch.

## Is CVE-2023-26085 being exploited?

There is no known exploitation of CVE-2023-26085 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-26085 and fix it if it is affected.

What it is: CVE-2023-26085 is a high-severity memory corruption vulnerability in n/a, published on 29 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-26085 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-26085/ (Markdown: https://insights.sbomify.com/CVE-2023-26085/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-26085
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-26085
- OSV: https://osv.dev/vulnerability/CVE-2023-26085

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-26085/
Summaries are generated and may contain mistakes; the official description above is the record.