media: chips-media: wave5: Fix Reports from Kernel Lock Validator (CVE-2026-97514) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-97514

media: chips-media: wave5: Fix Reports from Kernel Lock Validator

Answer in brief

CVE-2026-97514 records a Unknown severity vulnerability in media: chips-media: wave5: Fix Reports from Kernel Lock Validator. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 24, 2026Updated Sep 24, 2026Source checked Sep 25, 2026First seen by HOL Sep 25, 2026Material review Sep 24, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <629a937091ecf9c5c9f7a18f41cb0e6c778a7b2f \|\| >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <072beef6a19f9c84dc5a50c5499663a5734c1096 \|\| >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7d5d364f8b2dcc9b6b92456fb55632fde4a4d96f \|\| >=0 <6.12.111 \|\| >=0 <6.18.53	629a937091ecf9c5c9f7a18f41cb0e6c778a7b2f, 072beef6a19f9c84dc5a50c5499663a5734c1096, 7d5d364f8b2dcc9b6b92456fb55632fde4a4d96f, 6.12.111, 6.18.53

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux.
Review the reported fix. Update Linux/Linux to 629a937091ecf9c5c9f7a18f41cb0e6c778a7b2f if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 25, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.