# CVE-2026-97580: media: rkvdec: bound HEVC tile loops and PPS id to the array capacity

> An attacker can trigger out-of-bounds writes in the rkvdec driver via crafted HEVC parameters, potentially leading to code execution or privilege escalation.

- **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:** DEBIAN-CVE-2026-97580, GHSA-jwh6-9234-v665, UBUNTU-CVE-2026-97580

## What is CVE-2026-97580?

CVE-2026-97580 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: rkvdec: bound HEVC tile loops and PPS id to the array capacity

compute_tiles_uniform() and compute_tiles_non_uniform() loop over
num_tile_columns_minus1 + 1 / num_tile_rows_minus1 + 1 entries, and
assemble_hw_pps() writes one COLUMN_WIDTH / ROW_HEIGHT register per tile
and indexes priv_tbl->param_set[] by pic_parameter_set_id, all taken from
the untrusted PPS. Use the bounded v4l2_hevc_pps_num_tile_columns() /
v4l2_hevc_pps_num_tile_rows() helpers for the tile loops, and bail out of
assemble_hw_pps() before indexing priv_tbl->param_set[] with an
out-of-range pic_parameter_set_id, so the writes stay within the hardware
tables.

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


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

Apply the vendor's patch.

## Is CVE-2026-97580 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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