CVE-2026-23110 Details
Description
In the Linux kernel, the following vulnerability has been resolved: scsi: core: Wake up the error handler when final completions race against each other The fragile ordering between marking commands completed or failed so that the error handler only wakes when the last running command completes or times out has race conditions. These race conditions can cause the SCSI layer to fail to wake the error handler, leaving I/O through the SCSI host stuck as the error state cannot advance. First, there is an memory ordering issue within scsi_dec_host_busy(). The write which clears SCMD_STATE_INFLIGHT may be reordered with reads counting in scsi_host_busy(). While the local CPU will see its own write, reordering can allow other CPUs in scsi_dec_host_busy() or scsi_eh_inc_host_failed() to see a raised busy count, causing no CPU to see a host busy equal to the host_failed count. This race condition can be prevented with a memory barrier on the error path to force the write to be visible before counting host busy commands. Second, there is a general ordering issue with scsi_eh_inc_host_failed(). By counting busy commands before incrementing host_failed, it can race with a final command in scsi_dec_host_busy(), such that scsi_dec_host_busy() does not see host_failed incremented but scsi_eh_inc_host_failed() counts busy commands before SCMD_STATE_INFLIGHT is cleared by scsi_dec_host_busy(), resulting in neither waking the error handler task. This needs the call to scsi_host_busy() to be moved after host_failed is incremented to close the race condition.
A race condition vulnerability has been identified in the Linux kernel's SCSI (Small Computer System Interface) subsystem. This vulnerability arises from a fragile ordering process when marking commands as completed or failed, which can disrupt the error handling mechanism. As a result, the error handler may not be properly awakened, leaving SCSI input/output operations stalled because the error state cannot progress. The issue is rooted in memory ordering problems within the 'scsi_dec_host_busy()' function, where the write operation clearing the 'SCMD_STATE_INFLIGHT' state can be reordered. This reordering may cause other CPUs to misinterpret the busy state of commands, leading to a failure in recognizing that the host is no longer busy. Additionally, the 'scsi_eh_inc_host_failed()' function can create further ordering issues by counting busy commands before incrementing the failed command count, potentially causing the error handler not to be notified when it should be.
Users can apply the latest patches available in the Linux kernel stable tree to address this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jun 10, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-362 | Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') | [email protected] |
| CWE-362 | Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') | CISA-ADP |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.5, < 5.10.249 >= 5.11, < 6.1.162 >= 6.2, < 6.6.122 >= 6.7, < 6.12.68 >= 6.13, < 6.18.8 6.19 rc1 6.19 rc2 6.19 rc3 6.19 rc4 6.19 rc5 6.19 rc6 |
CPE
Remediation
| |
Change History
12 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 10, 2026 | CVE Modified | siemens-SADP |
| Oct 19, 2026 | CVE Modified | CISA-ADP |
| Oct 15, 2026 | CVE Modified | siemens-SADP |
| Oct 15, 2026 | CVE Modified | kernel.org |
| Jul 14, 2026 | CVE Modified | siemens-SADP |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| May 4, 2026 | CVE Modified | kernel.org |
| Apr 18, 2026 | CVE Modified | kernel.org |
| Mar 18, 2026 | Initial Analysis | [email protected] |
| Feb 6, 2026 | CVE Modified | kernel.org |
| Feb 4, 2026 | New CVE Received | kernel.org |