# CVE-2026-97575: media: v4l2-ctrls: validate AV1 tile counts

> Missing validation of AV1 tile counts in the Linux kernel allows attackers to trigger integer overflows, potentially causing crashes or code execution.

- **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-104780, BELL-CVE-2026-97575, DEBIAN-CVE-2026-97575, GHSA-fhp7-73g8-wj3g, UBUNTU-CVE-2026-97575

## What is CVE-2026-97575?

CVE-2026-97575 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 AV1 tile counts

The stateless AV1 decoders use tile_info.tile_cols and tile_rows as loop
bounds and as indices into the mi_*_starts[] and *_in_sbs_minus_1[]
arrays, as the divisor for context_update_tile_id, and their product
bounds the per-tile descriptor buffers, but std_validate_compound() does
not bound these u8 fields. Reject a V4L2_CTRL_TYPE_AV1_FRAME whose
tile_cols or tile_rows exceeds V4L2_AV1_MAX_TILE_COLS / _ROWS, or whose
product exceeds V4L2_AV1_MAX_TILE_COUNT. A zero tile count is left to the
consuming driver so the zero-initialised control that existing userspace
submits is still accepted.

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


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

Apply the vendor's patch.

## Is CVE-2026-97575 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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