# CVE-2026-97576: media: v4l2-ctrls: validate HEVC tile counts

> A missing validation in the Linux kernel HEVC decoder allows attackers to cause a denial of service via crafted tile counts.

- **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-104399, BELL-CVE-2026-97576, DEBIAN-CVE-2026-97576, GHSA-f66p-93rc-m283, UBUNTU-CVE-2026-97576

## What is CVE-2026-97576?

CVE-2026-97576 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: v4l2-ctrls: validate HEVC tile counts

The stateless HEVC decoders read num_tile_columns_minus1 + 1 entries from
column_width_minus1[] and num_tile_rows_minus1 + 1 from row_height_minus1[]
and use them as tile-loop bounds, but std_validate_compound() does not
bound these u8 counts. Reject a V4L2_CTRL_TYPE_HEVC_PPS with tiling
enabled whose tile counts exceed the uAPI array capacity, mirroring the
existing compound-control range checks.

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


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

Apply the vendor's patch.

## Is CVE-2026-97576 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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