cbcvebase.
CVE-2026-23110
published 2026-02-04

CVE-2026-23110: 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…

PriorityP418medium4.7CVSS 3.1
AVLACHPRLUINSUCNINAH
EPSS
0.10%
0.8th percentile
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.

Affected

53 ranges· showing 25
VendorProductVersion rangeFixed in
debianlinux< linux 6.1.162-1 (bookworm)linux 6.1.162-1 (bookworm)
debianlinux-6.1< linux 6.1.162-1 (bookworm)linux 6.1.162-1 (bookworm)
linuxlinux
linuxlinux>= 6eb045e092efefafc6687409a6fa6d1dabf0fb69 < cc872e35c0df80062abc71268d690a2f749e542ecc872e35c0df80062abc71268d690a2f749e542e
linuxlinux>= 6eb045e092efefafc6687409a6fa6d1dabf0fb69 < 6d9a367be356101963c249ebf10ea10b328866076d9a367be356101963c249ebf10ea10b32886607
linuxlinux>= 6eb045e092efefafc6687409a6fa6d1dabf0fb69 < 9fdc6f28d5e81350ab1d2cac8389062bd09e61e19fdc6f28d5e81350ab1d2cac8389062bd09e61e1
linuxlinux>= 6eb045e092efefafc6687409a6fa6d1dabf0fb69 < 64ae21b9c4f0c7e60cf47a53fa7ab68852079ef064ae21b9c4f0c7e60cf47a53fa7ab68852079ef0
linuxlinux>= 6eb045e092efefafc6687409a6fa6d1dabf0fb69 < 219f009ebfd1ef3970888ee9eef4c8a06357f862219f009ebfd1ef3970888ee9eef4c8a06357f862
linuxlinux>= 6eb045e092efefafc6687409a6fa6d1dabf0fb69 < fe2f8ad6f0999db3b318359a01ee0108c703a8c3fe2f8ad6f0999db3b318359a01ee0108c703a8c3
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel>= 0 < 5.10.249-15.10.249-1
linuxlinux_kernel>= 0 < 6.1.162-16.1.162-1
linuxlinux_kernel>= 0 < 6.12.69-16.12.69-1
linuxlinux_kernel>= 0 < 6.18.8-16.18.8-1
linuxlinux_kernel>= 5.11 < 6.1.1626.1.162
linuxlinux_kernel>= 5.5 < 5.10.2495.10.249
linuxlinux_kernel>= 6.13 < 6.18.86.18.8
linuxlinux_kernel>= 6.2 < 6.6.1226.6.122
linuxlinux_kernel>= 6.7 < 6.12.686.12.68
msrccbl2_kernel_5.15.200.1-1_on_cbl_mariner_2.0

CVSS provenance

nvdv3.14.7MEDIUMCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
osv4.7MEDIUM
vendor_ubuntu7.8HIGH
vendor_debian4.7MEDIUM
vendor_msrc4.7MEDIUM
vendor_redhat4.7MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.