{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89980 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89980 is a high-severity vulnerability in Linux, published on 16 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-89980 and fix it if it is affected.\n\nWhat it is: CVE-2026-89980 is a high-severity vulnerability in Linux, published on 16 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-89980 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-89980/ (Markdown: https://insights.sbomify.com/CVE-2026-89980/index.md)","id":"CVE-2026-89980","markdown":"https://insights.sbomify.com/CVE-2026-89980/index.md","name":"CVE-2026-89980","record":{"aliases":["AZL-101262","BELL-CVE-2026-89980","DEBIAN-CVE-2026-89980","GHSA-w4v8-wqj5-pmgx","UBUNTU-CVE-2026-89980"],"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 race condition in the ALSA harmony driver allows a pending interrupt to access uninitialized locks, potentially causing a kernel crash.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nALSA: harmony: initialize locks before requesting IRQ\n\nsnd_harmony_create() registers the IRQ before initializing h-\u003elock and\nh-\u003emixer_lock. A pending interrupt can invoke the handler while these\nlocks are uninitialized.\n\nInitialize both locks before requesting the IRQ so the handler always\nsees valid lock state.","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":"ALSA: harmony: initialize locks before requesting IRQ","id":"CVE-2026-89980","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"arm64: Don't read GMID_EL1 when MTE is disabled","id":"CVE-2026-89981"},"packages":[],"prev":{"headline":"ALSA: pcm: Fix race between non-atomic ops and trigger-start","id":"CVE-2026-89979"},"products":["Linux"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A race condition in the ALSA harmony driver allows a pending interrupt to access uninitialized locks, potentially causing a kernel crash.","url":"https://insights.sbomify.com/CVE-2026-89980/"}