# CVE-2026-97514: media: chips-media: wave5: Fix Reports from Kernel Lock Validator

> A locking error in the wave5 media driver can cause kernel deadlocks or crashes, requiring local access to exploit.

- **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:** 24 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** AZL-103622, BELL-CVE-2026-97514, DEBIAN-CVE-2026-97514, GHSA-8mx9-7h8g-9qqg, UBUNTU-CVE-2026-97514

## What is CVE-2026-97514?

CVE-2026-97514 is a vulnerability in Linux, published on 24 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: chips-media: wave5: Fix Reports from Kernel Lock Validator

handle_dynamic_resolution change requires that the state_lock be acquired
based on the lockdep_assert_held. However, the
handle_dynamic_resolution_change call in initialize_sequence does not
properly obtain the lock before calling.

Since the v4l2_ctrl_find and s_ctrl can sleep, they should not be called
while a lock is already held. Store off the fbc_buf_count then properly
update control once lock has been freed.

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


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

Apply the vendor's patch.

## Is CVE-2026-97514 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97514 is a vulnerability in Linux, published on 24 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-97514 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-97514/ (Markdown: https://insights.sbomify.com/CVE-2026-97514/index.md)
```

## Sources

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

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