# CVE-2026-97581: media: verisilicon: hantro: bound G2 HEVC tile loop to the buffer capacity

> A buffer overflow in the Linux kernel Hantro HEVC driver allows attackers to cause memory corruption, potentially leading to code execution or system crashes.

- **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:** 19 Oct 2026
- **Also known as:** AZL-104826, BELL-CVE-2026-97581, DEBIAN-CVE-2026-97581, GHSA-g7px-hwh6-xc48, UBUNTU-CVE-2026-97581

## What is CVE-2026-97581?

CVE-2026-97581 is a 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: hantro: bound G2 HEVC tile loop to the buffer capacity

prepare_tile_info_buffer() writes one entry per tile into the tile_sizes
DMA buffer, sized for a grid equal to the PPS uAPI array capacity. Use the
bounded v4l2_hevc_pps_num_tile_columns() / v4l2_hevc_pps_num_tile_rows()
helpers so the loops stay inside the buffer.

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


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

Apply the vendor's patch.

## Is CVE-2026-97581 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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