{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93091 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93091 is an use after free 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-93091 and fix it if it is affected.\n\nWhat it is: CVE-2026-93091 is an use after free 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-93091 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-93091/ (Markdown: https://insights.sbomify.com/CVE-2026-93091/index.md)","id":"CVE-2026-93091","markdown":"https://insights.sbomify.com/CVE-2026-93091/index.md","name":"CVE-2026-93091","record":{"aliases":["AZL-102393","BELL-CVE-2026-93091","DEBIAN-CVE-2026-93091","GHSA-634x-xgvq-4p3j","UBUNTU-CVE-2026-93091"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A use-after-free vulnerability in the Linux kernel's SCMI driver allows local attackers to cause denial of service or execute code during device teardown.","user_interaction":"not_required","vuln_class":"use_after_free"},"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\nfirmware: arm_scmi: Quiesce notifications before teardown\n\nscmi_notification_exit() clears and releases the notification instance,\nbut transport callbacks can still deliver incoming notifications until\nthe TX/RX channels are freed. During remove, an RX interrupt in that\nwindow can enter scmi_notify() while notification state is being torn\ndown and then dereference freed memory. The same ordering exists on the\nprobe error path after notification initialization.\n\nThe notification late-init worker has a separate lifetime issue: protocol\nevent registration queues ni-\u003einit_work on the system workqueue, so\ndestroying ni-\u003enotify_wq does not drain that work. If the devres group is\nreleased while init_work is still pending or running, the late-init worker\ncan dereference the freed notification instance.\n\nQuiesce the notification core before TX/RX channels are torn down, then\nclean up the channels before releasing the notification core resources.\nUse disable_work_sync() so future late-init queueing is rejected and any\nalready queued or running late-init work has completed before channel\nteardown starts.","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":"firmware: arm_scmi: Quiesce notifications before teardown","id":"CVE-2026-93091","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"firmware: arm_scmi: Unregister device notifier before IDR teardown","id":"CVE-2026-93092"},"packages":[],"prev":{"headline":"firmware: arm_scmi: Clean up channels on setup failure","id":"CVE-2026-93090"},"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 use-after-free vulnerability in the Linux kernel's SCMI driver allows local attackers to cause denial of service or execute code during device teardown.","url":"https://insights.sbomify.com/CVE-2026-93091/"}