{"id":"CVE-2026-23110","summary":"scsi: core: Wake up the error handler when final completions race against each other","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: core: Wake up the error handler when final completions race against each other\n\nThe fragile ordering between marking commands completed or failed so\nthat the error handler only wakes when the last running command\ncompletes or times out has race conditions. These race conditions can\ncause the SCSI layer to fail to wake the error handler, leaving I/O\nthrough the SCSI host stuck as the error state cannot advance.\n\nFirst, there is an memory ordering issue within scsi_dec_host_busy().\nThe write which clears SCMD_STATE_INFLIGHT may be reordered with reads\ncounting in scsi_host_busy(). While the local CPU will see its own\nwrite, reordering can allow other CPUs in scsi_dec_host_busy() or\nscsi_eh_inc_host_failed() to see a raised busy count, causing no CPU to\nsee a host busy equal to the host_failed count.\n\nThis race condition can be prevented with a memory barrier on the error\npath to force the write to be visible before counting host busy\ncommands.\n\nSecond, there is a general ordering issue with scsi_eh_inc_host_failed(). By\ncounting busy commands before incrementing host_failed, it can race with a\nfinal command in scsi_dec_host_busy(), such that scsi_dec_host_busy() does\nnot see host_failed incremented but scsi_eh_inc_host_failed() counts busy\ncommands before SCMD_STATE_INFLIGHT is cleared by scsi_dec_host_busy(),\nresulting in neither waking the error handler task.\n\nThis needs the call to scsi_host_busy() to be moved after host_failed is\nincremented to close the race condition.","modified":"2026-04-19T04:15:59.979342Z","published":"2026-02-04T16:08:30.158Z","related":["SUSE-SU-2026:0962-1","SUSE-SU-2026:1081-1","SUSE-SU-2026:20667-1","SUSE-SU-2026:20720-1","SUSE-SU-2026:20838-1","SUSE-SU-2026:20845-1","SUSE-SU-2026:20876-1","SUSE-SU-2026:20931-1","openSUSE-SU-2026:20416-1"],"database_specific":{"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23110.json","cna_assigner":"Linux"},"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/219f009ebfd1ef3970888ee9eef4c8a06357f862"},{"type":"WEB","url":"https://git.kernel.org/stable/c/48cbc304c5ea796421f7d10b7798fa581970c080"},{"type":"WEB","url":"https://git.kernel.org/stable/c/64ae21b9c4f0c7e60cf47a53fa7ab68852079ef0"},{"type":"WEB","url":"https://git.kernel.org/stable/c/6d9a367be356101963c249ebf10ea10b32886607"},{"type":"WEB","url":"https://git.kernel.org/stable/c/9fdc6f28d5e81350ab1d2cac8389062bd09e61e1"},{"type":"WEB","url":"https://git.kernel.org/stable/c/fe2f8ad6f0999db3b318359a01ee0108c703a8c3"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23110.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23110"},{"type":"FIX","url":"https://git.kernel.org/stable/c/cc872e35c0df80062abc71268d690a2f749e542e"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"6eb045e092efefafc6687409a6fa6d1dabf0fb69"},{"fixed":"48cbc304c5ea796421f7d10b7798fa581970c080"},{"fixed":"6d9a367be356101963c249ebf10ea10b32886607"},{"fixed":"9fdc6f28d5e81350ab1d2cac8389062bd09e61e1"},{"fixed":"64ae21b9c4f0c7e60cf47a53fa7ab68852079ef0"},{"fixed":"219f009ebfd1ef3970888ee9eef4c8a06357f862"},{"fixed":"fe2f8ad6f0999db3b318359a01ee0108c703a8c3"}]}],"database_specific":{"source":"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-23110.json"}}],"schema_version":"1.7.5"}