{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89945 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89945 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-89945 and fix it if it is affected.\n\nWhat it is: CVE-2026-89945 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-89945 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-89945/ (Markdown: https://insights.sbomify.com/CVE-2026-89945/index.md)","id":"CVE-2026-89945","markdown":"https://insights.sbomify.com/CVE-2026-89945/index.md","name":"CVE-2026-89945","record":{"aliases":["AZL-101454","BELL-CVE-2026-89945","DEBIAN-CVE-2026-89945","GHSA-w3mv-pmf4-r863","UBUNTU-CVE-2026-89945"],"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 Linux kernel cs35l34 audio codec driver allows a local attacker to cause a denial of service by triggering a use-after-free scenario during runtime suspend.","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\nASoC: cs35l34: drain threaded IRQ before runtime suspend\n\ncs35l34_runtime_suspend() currently switches the codec into\nregcache_cache_only(true), asserts reset low, and powers the device off\nwithout first quiescing the threaded IRQ registered by\ndevm_request_threaded_irq(). That leaves a window where\ncs35l34_irq_thread() can still run after suspend has removed live\nhardware access.\n\nA running system can reach this during runtime PM while the driver still\nhas critical fault IRQs unmasked. If the threaded handler runs in that\nwindow, it reads volatile INT_STATUS_1..4 after cache_only has been\nenabled, ignores the regmap_read() failures, and can still execute the\nPROT_RELEASE_CTL release sequence or the BST fault power-down writes.\n\nUse disable_irq() before entering cache_only/reset-low/power-off so any\nin-flight threaded handler is drained and no new IRQ thread can run\nwhile the device is suspended. Re-enable the IRQ only after\nruntime_resume() has restored live register access with regcache_sync().\nSince probe only logs request_threaded_irq() failures and keeps going,\ntrack whether the IRQ was actually installed before disabling or\nre-enabling it.","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":"ASoC: cs35l34: drain threaded IRQ before runtime suspend","id":"CVE-2026-89945","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"ASoC: cs35l33: drain threaded IRQ before runtime suspend","id":"CVE-2026-89946"},"packages":[],"prev":{"headline":"ASoC: hdac_hda: Fix hlink refcount leak on component registration failure","id":"CVE-2026-89944"},"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 Linux kernel cs35l34 audio codec driver allows a local attacker to cause a denial of service by triggering a use-after-free scenario during runtime suspend.","url":"https://insights.sbomify.com/CVE-2026-89945/"}