{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93781 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93781 is a denial of service vulnerability in Linux, published on 24 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-93781 and fix it if it is affected.\n\nWhat it is: CVE-2026-93781 is a denial of service vulnerability in Linux, published on 24 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-93781 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-93781/ (Markdown: https://insights.sbomify.com/CVE-2026-93781/index.md)","id":"CVE-2026-93781","markdown":"https://insights.sbomify.com/CVE-2026-93781/index.md","name":"CVE-2026-93781","record":{"aliases":["AZL-103550","BELL-CVE-2026-93781","DEBIAN-CVE-2026-93781","GHSA-3mhv-m8g9-8q53","UBUNTU-CVE-2026-93781"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A deadlock in the Linux kernel SCSI error handler can cause a denial of service by blocking I/O operations when tags are exhausted.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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\nscsi: core: Do not block on tag allocation in scsi_eh_lock_door()\n\nscsi_eh_lock_door() is called from scsi_restart_operations() while the\nhost is still in the SHOST_RECOVERY state, i.e. before the host is\nswitched back to SHOST_RUNNING and scsi_run_host_queues() restarts the\nqueues. It allocates a request via scsi_alloc_request() with no flags,\nso blk_mq_get_tag() may block waiting for a free sched tag when all tags\nare already in use.\n\nThose tags can be held by commands that were just requeued by\nscsi_eh_flush_done_q() during error handling. Such commands cannot be\ndispatched until the host leaves SHOST_RECOVERY and\nscsi_run_host_queues() is called - which only happens *after*\nscsi_eh_lock_door() returns.\n\nThis forms a circular dependency:\n\n  - scsi_eh_lock_door(), running in the SCSI error handler thread, waits\n    for a sched tag held by a requeued command;\n\n  - the requeued command cannot complete and release its sched tag until\n    the error handler thread leaves scsi_restart_operations() and restart\n    the queues.\n\nFor devices with a single driver tag (e.g. USB storage) it is a\nguaranteed deadlock and I/O that can never be submitted. This problem\nhas also been reproduced in our environment.\n\nLocking the door is a best-effort operation, and scsi_eh_lock_door()\nalready returns silently when the request allocation fails. Pass\nBLK_MQ_REQ_NOWAIT to scsi_alloc_request() so the allocation fails\ninstead of blocking when no tag is available. This breaks the circular\ndependency and allows the error handler to finish restarting the queues,\nafter which the pending commands are dispatched normally.","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":"scsi: core: Do not block on tag allocation in scsi_eh_lock_door()","id":"CVE-2026-93781","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"vhost-scsi: flush backend after device ioctls","id":"CVE-2026-93782"},"packages":[],"prev":{"headline":"Cross-site scripting in WP Yelp Review Slider","id":"CVE-2026-93778"},"products":["Linux"],"published":"2026-09-24","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-03","vendors":["Linux"]},"summary":"A deadlock in the Linux kernel SCSI error handler can cause a denial of service by blocking I/O operations when tags are exhausted.","url":"https://insights.sbomify.com/CVE-2026-93781/"}