{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97514 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-97514 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-97514 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-97514/ (Markdown: https://insights.sbomify.com/CVE-2026-97514/index.md)","id":"CVE-2026-97514","markdown":"https://insights.sbomify.com/CVE-2026-97514/index.md","name":"CVE-2026-97514","record":{"aliases":["AZL-103622","BELL-CVE-2026-97514","DEBIAN-CVE-2026-97514","GHSA-8mx9-7h8g-9qqg","UBUNTU-CVE-2026-97514"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A locking error in the wave5 media driver can cause kernel deadlocks or crashes, requiring local access to exploit.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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_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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"media: chips-media: wave5: Fix Reports from Kernel Lock Validator","id":"CVE-2026-97514","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"i3c: master: svc: Prevent IRQ storm from false SLVSTART on NPCM845","id":"CVE-2026-97515"},"packages":[],"prev":{"headline":"media: chips-media: wave5: Release m2m_ctx after Instance Removed from List","id":"CVE-2026-97513"},"products":["Linux"],"published":"2026-09-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-09-28","vendors":["Linux"]},"summary":"A locking error in the wave5 media driver can cause kernel deadlocks or crashes, requiring local access to exploit.","url":"https://insights.sbomify.com/CVE-2026-97514/"}