# CVE-2026-97911: accel: ethosu: Ensure SRAM region size matches job

> A local attacker can access stale SRAM memory from previous jobs by setting the job SRAM size to zero, bypassing intended memory isolation in the Ethos-U accelerator driver.

- **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:** 25 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-97911, GHSA-q5mm-h94w-h3jf, UBUNTU-CVE-2026-97911

## What is CVE-2026-97911?

CVE-2026-97911 is a high-severity missing authorization 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 region size matches job

It is possible for userspace to set the job SRAM size to 0, but then still
have SRAM accesses in the command stream. When the job SRAM size is 0,
setting the region base register is skipped and a stale base address from
a prior job is used.

Check the region size against the job's SRAM size instead of just the size
of the SRAM. The job's SRAM size was already checked against the total SRAM
size.

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


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

Apply the vendor's patch.

## Is CVE-2026-97911 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97911 is a high-severity missing authorization 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-97911 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-97911/ (Markdown: https://insights.sbomify.com/CVE-2026-97911/index.md)
```

## Sources

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

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