# CVE-2026-97577: media: verisilicon: rockchip: reject AV1 frames exceeding the tile capacity

> A missing bounds check in the Rockchip AV1 decoder allows out-of-bounds reads and potential memory corruption when processing malicious video frames.

- **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-110473, BELL-CVE-2026-97577, DEBIAN-CVE-2026-97577, GHSA-jj87-p9c8-ffw2, UBUNTU-CVE-2026-97577

## What is CVE-2026-97577?

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

media: verisilicon: rockchip: reject AV1 frames exceeding the tile capacity

rockchip_vpu981_av1_dec_set_tile_info() indexes the tile group entry
array by tile1 * tile_cols + tile0, reading up to tile_cols * tile_rows
entries, lays out one descriptor per tile in the AV1_MAX_TILES tile_info
buffer, and programs the real tile_cols / tile_rows into the hardware.

The tile group entry control is a dynamic array sized to the number of
entries userspace submitted, independent of tile_cols / tile_rows, so a
frame that claims more tiles than entries reads past the array. A frame
that claims more than AV1_MAX_TILES tiles also leaves the hardware
programmed for more tiles than the descriptor buffer holds.

Reject both in prepare_run(): tile_cols * tile_rows must not exceed the
submitted entry count or AV1_MAX_TILES. The entry count is read via
v4l2_ctrl_find() (ctrl->elems). This mirrors the bound the mediatek AV1
decoder already enforces.

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


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

Apply the vendor's patch.

## Is CVE-2026-97577 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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