# CVE-2026-97912: accel: ethosu: Ensure SRAM size is 0 on mapping failure

> A Linux kernel driver flaw allows unauthorized memory access to physical address zero, potentially enabling code execution or privilege escalation.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-97912, GHSA-3c99-6rw9-787g, UBUNTU-CVE-2026-97912

## What is CVE-2026-97912?

CVE-2026-97912 is a memory corruption vulnerability in Linux, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

accel: ethosu: Ensure SRAM size is 0 on mapping failure

On a mapping failure of the SRAM, the SRAM size is left as non-zero. The
probe will succeed as the error return is not checked since having SRAM is
not a hard requirement. The non-zero size allows jobs to access SRAM which
is left pointing to physical base address 0x0.

## Which versions are affected by CVE-2026-97912?


## How do I fix CVE-2026-97912?

Apply the vendor's patch.

## Is CVE-2026-97912 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97912 and fix it if it is affected.

What it is: CVE-2026-97912 is a memory corruption vulnerability in Linux, published on 25 Sep 2026. 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-2026-97912 in the wild and no public exploit code.

Affected product: Linux. 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-2026-97912/ (Markdown: https://insights.sbomify.com/CVE-2026-97912/index.md)
```

## Sources

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

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