{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93185 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93185 is a vulnerability in Linux, published on 17 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-93185 and fix it if it is affected.\n\nWhat it is: CVE-2026-93185 is a vulnerability in Linux, published on 17 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-93185 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-93185/ (Markdown: https://insights.sbomify.com/CVE-2026-93185/index.md)","id":"CVE-2026-93185","markdown":"https://insights.sbomify.com/CVE-2026-93185/index.md","name":"CVE-2026-93185","record":{"aliases":["AZL-102152","BELL-CVE-2026-93185","DEBIAN-CVE-2026-93185","GHSA-87fr-rh89-2wmg","UBUNTU-CVE-2026-93185"],"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's rt700-sdw driver can cause a denial of service if jack work is not drained during device removal.","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: rt700-sdw: always drain jack work on remove\n\nrt700_sdw_remove() drains jack_detect_work and jack_btn_check_work only\nwhen rt700-\u003ehw_init is true. That state bit is cleared by\nrt700_update_status() when the SoundWire slave becomes UNATTACHED, but a\njack work item can already have been queued by rt700_interrupt_callback()\nor rt700_jack_init() while the device was initialized.\n\nDo not use hw_init as the remove-time guard for draining these work\nobjects. The delayed works are initialized during rt700_init(), so remove\ncan cancel them unconditionally and pair the object lifetime with the\ncodec-private data lifetime instead of a mutable hardware state bit.\n\nThis issue was found by our static analysis tool and then confirmed by\nmanual review of the SoundWire status, interrupt and remove paths. The\nremove path should drain work based on whether the work object exists, not\non a runtime hardware state bit that can change after the work was queued.\n\nA QEMU PoC queued jack_detect_work, simulated SDW_SLAVE_UNATTACHED, and\nthen entered remove. DEBUG_OBJECTS reported an active timer/work object\nassociated with the rt700 jack work path after remove skipped the cancel.\n\nThis is sent as an RFC because the practical trigger depends on SoundWire\ncore remove ordering after an UNATTACHED status update. If remove cannot\nrun after hw_init has been cleared while jack work is still pending, this\nis a defensive lifecycle cleanup rather than a reachable race on current\nsystems.","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: rt700-sdw: always drain jack work on remove","id":"CVE-2026-93185","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":"cxl/mbox: Clamp mailbox output allocation to the payload size","id":"CVE-2026-93186"},"packages":[],"prev":{"headline":"ASoC: fsl_audmix: rework runtime PM handling in probe","id":"CVE-2026-93184"},"products":["Linux"],"published":"2026-09-17","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's rt700-sdw driver can cause a denial of service if jack work is not drained during device removal.","url":"https://insights.sbomify.com/CVE-2026-93185/"}