# CVE-2026-97917: accel/ivpu: Validate full buffer range in ivpu_to_cpu_addr

> A missing bounds check in the Linux kernel's Intel VPU driver allows local attackers to trigger memory corruption, potentially leading to privilege escalation or code execution.

- **Severity:** Not scored
- **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:** 21 Oct 2026
- **Also known as:** AZL-104315, BELL-CVE-2026-97917, DEBIAN-CVE-2026-97917, GHSA-pr47-mr9h-9c89, UBUNTU-CVE-2026-97917

## What is CVE-2026-97917?

CVE-2026-97917 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/ivpu: Validate full buffer range in ivpu_to_cpu_addr

Add a size parameter to ivpu_to_cpu_addr() and validate that the
whole [vpu_addr, vpu_addr + size) range stays within the BO.

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


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

Apply the vendor's patch.

## Is CVE-2026-97917 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97917 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-97917 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-97917/ (Markdown: https://insights.sbomify.com/CVE-2026-97917/index.md)
```

## Sources

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

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