# CVE-2026-97915: accel/ivpu: Limit firmware log name prints to field size

> A missing NUL-termination check in the Linux kernel's Intel VPU driver allows local attackers to read adjacent memory via debug logs.

- **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:** 21 Oct 2026
- **Also known as:** AZL-104256, BELL-CVE-2026-97915, DEBIAN-CVE-2026-97915, GHSA-qr56-qc89-442x, UBUNTU-CVE-2026-97915

## What is CVE-2026-97915?

CVE-2026-97915 is a 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: Limit firmware log name prints to field size

The name in struct vpu_tracing_buffer_header is a fixed-size array
populated by the NPU firmware. It is expected to be NUL-terminated,
but nothing on the host side enforces this, so printing it with an
unbounded string conversion would read past the field if the
terminator is ever missing and expose adjacent bytes of the shared
tracing BO through dmesg and the debugfs FW log output.

Print at most as many characters as the name field holds, so the output
never runs past it even if the string is not NUL-terminated.

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


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

Apply the vendor's patch.

## Is CVE-2026-97915 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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