{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89869 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89869 is a 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-89869 and fix it if it is affected.\n\nWhat it is: CVE-2026-89869 is a 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-89869 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-89869/ (Markdown: https://insights.sbomify.com/CVE-2026-89869/index.md)","id":"CVE-2026-89869","markdown":"https://insights.sbomify.com/CVE-2026-89869/index.md","name":"CVE-2026-89869","record":{"aliases":["BELL-CVE-2026-89869","DEBIAN-CVE-2026-89869","GHSA-5mhw-wrx9-mqjj","UBUNTU-CVE-2026-89869"],"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 Qualcomm Iris VPU driver allows hardware register access after power-off, potentially causing system instability or denial of service.","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: qcom: iris: use disable_irq() during power-off\n\nThe IRQ is registered as a threaded IRQ.\n\nUsing disable_irq_nosync() in iris_vpu_power_off() does not wait\nfor an already queued threaded IRQ handler to complete before\nreturning.\n\nAs a result, a threaded IRQ handler may still run after the VPU has\nbeen powered down and access hardware registers after power-off.\n\nReplace disable_irq_nosync() with disable_irq() so the power-off path\nwaits for any in-flight threaded IRQ handler to complete before\nreturning.","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: qcom: iris: use disable_irq() during power-off","id":"CVE-2026-89869","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":"media: zoran: Avoid freeing a registered video_device twice","id":"CVE-2026-89870"},"packages":[],"prev":{"headline":"media: chips-media: wave5: Add timeout while stop_streaming","id":"CVE-2026-89868"},"products":["Linux"],"published":"2026-09-16","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-10-19","vendors":["Linux"]},"summary":"A race condition in the Qualcomm Iris VPU driver allows hardware register access after power-off, potentially causing system instability or denial of service.","url":"https://insights.sbomify.com/CVE-2026-89869/"}