CVE-2026-97514
Linux: media: chips-media: wave5: Fix Reports from Kernel Lock Validator
CVSS
NoneNot scoredExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.15%Chance of exploitation activity in the next 30 days, higher than 4% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in629a937091ecf9c5c9f7a18f41cb0e6c778a7b2fAlso 072beef6a19f9c84dc5a50c5499663a5734c1096, 7d5d364f8b2dcc9b6b92456fb55632fde4a4d96fCVE List
What fixes it
- 629a937091ecf9c5c9f7a18f41cb0e6c778a7b2fLinuxCVE List
- 072beef6a19f9c84dc5a50c5499663a5734c1096LinuxCVE List
- 7d5d364f8b2dcc9b6b92456fb55632fde4a4d96fLinuxCVE List
A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.
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.
Text from CVE List
Affected versions 8
- Linuxaffected: 9707a6254a8a6b978bde811a44fe07d86c229d1c before 629a937091ecf9c5c9f7a18f41cb0e6c778a7b2fCVE List
- Linuxaffected: 9707a6254a8a6b978bde811a44fe07d86c229d1c before 072beef6a19f9c84dc5a50c5499663a5734c1096CVE List
- Linuxaffected: 9707a6254a8a6b978bde811a44fe07d86c229d1c before 7d5d364f8b2dcc9b6b92456fb55632fde4a4d96fCVE List
- Linuxaffected: 6.8CVE List
- Linuxunaffected: all versions before 6.8CVE List
- Linuxunaffected: 6.12.111 through 6.12.*CVE List
- Linuxunaffected: 6.18.53 through 6.18.*CVE List
- Linuxunaffected: 7.2CVE List