# CVE-2026-89730: fpga: altera-cvp: Avoid out-of-bounds read in trailing byte write

> A local attacker can trigger a kernel crash by exploiting an out-of-bounds read in the Altera CVP FPGA driver during image loading.

- **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:** 11 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-100439, BELL-CVE-2026-89730, DEBIAN-CVE-2026-89730, GHSA-f682-7h79-jmqf, UBUNTU-CVE-2026-89730

## What is CVE-2026-89730?

CVE-2026-89730 is a memory corruption vulnerability in Linux, published on 11 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:

fpga: altera-cvp: Avoid out-of-bounds read in trailing byte write

The trailing byte path in altera_cvp_send_block() dereferences a u32
pointer even when only 1-3 bytes remain in the input buffer. If the buffer
ends at a page or scatterlist boundary, this can read past the valid image
data and fault.

Copy the remaining bytes into a zero-initialized u32 before writing the
final word so only valid bytes are read from the input buffer.

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


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

Apply the vendor's patch.

## Is CVE-2026-89730 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89730 is a memory corruption vulnerability in Linux, published on 11 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-89730 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-89730/ (Markdown: https://insights.sbomify.com/CVE-2026-89730/index.md)
```

## Sources

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

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