# CVE-2026-97578: media: verisilicon: rockchip: guard VPU981 AV1 divisor and tile buffer

> A missing guard in the Rockchip VPU981 AV1 decoder allows division by zero or buffer overflow via crafted bitstreams, causing a kernel crash.

- **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:** AZL-104541, BELL-CVE-2026-97578, DEBIAN-CVE-2026-97578, GHSA-cr7v-wxrv-gp29, UBUNTU-CVE-2026-97578

## What is CVE-2026-97578?

CVE-2026-97578 is a high-severity 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:

media: verisilicon: rockchip: guard VPU981 AV1 divisor and tile buffer

rockchip_vpu981_av1_dec_set_tile_info() divides context_update_tile_id by
tile_info->tile_cols and writes one descriptor per tile into the tile_info
DMA buffer, which holds AV1_MAX_TILES entries; tile_cols and tile_rows
come from the bitstream. Guard the division against a zero tile_cols by
initialising the context-update values to zero and computing them only
when tile_cols is non-zero, and stop the descriptor writes once the
tile_info buffer is full. The tile geometry written to the hardware
registers is left unmodified; the per-dimension and total tile bounds are
enforced by the control validation.

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


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

Apply the vendor's patch.

## Is CVE-2026-97578 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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