{"id":"CVE-2026-97514","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: chips-media: wave5: Fix Reports from Kernel Lock Validator\n\nhandle_dynamic_resolution change requires that the state_lock be acquired\nbased on the lockdep_assert…","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: chips-media: wave5: Fix Reports from Kernel Lock Validator\n\nhandle_dynamic_resolution change requires that the state_lock be acquired\nbased 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","slug":"CVE-2026-97514","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: chips-media: wave5: Fix Reports from Kernel Lock Validator\n\nhandle_dynamic_resolution change requires that the state_lock be acquired\nbased on the lockdep_assert_held. However, the\nhandle_dynamic_resolution_change call in initialize_sequence does not\nproperly obtain the lock before calling.\n\nSince the v4l2_ctrl_find and s_ctrl can sleep, they should not be called\nwhile a lock is already held. Store off the fbc_buf_count then properly\nupdate control once lock has been freed.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}