---
id: CVE-2026-97514
title: |-
  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…
summary: |-
  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…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <
    629a937091ecf9c5c9f7a18f41cb0e6c778a7b2f
  - >-
    Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <
    072beef6a19f9c84dc5a50c5499663a5734c1096
  - >-
    Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <
    7d5d364f8b2dcc9b6b92456fb55632fde4a4d96f
  - Linux < 6.12.111
  - Linux < 6.18.53
  - Linux (all versions)
published: '2026-09-24'
updated: '2026-09-24'
sourceUpdated: '2026-09-24T17:17:29.323'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-97514'
references:
  - url: 'https://git.kernel.org/stable/c/072beef6a19f9c84dc5a50c5499663a5734c1096'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/629a937091ecf9c5c9f7a18f41cb0e6c778a7b2f'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/7d5d364f8b2dcc9b6b92456fb55632fde4a4d96f'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-24T16:47:15.860Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.