CVE-2026-23110

Local SCSI I/O hang via completion race

Published Feb 4, 2026 · Updated Feb 4, 2026

A race condition in the Linux kernel SCSI core allows local users to leave I/O through a SCSI host stuck after command errors. In scsi_dec_host_busy(), clearing SCMD_STATE_INFLIGHT can be observed after host-busy reads, while scsi_eh_inc_host_failed() counts busy commands before incrementing host_failed. When final failed and completed commands race, neither CPU wakes the error-handler task, so the host error state cannot advance and affected storage I/O remains hung.

CVSS severity4.7
Medium
EPSS probability0.10%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

A race condition in the Linux kernel SCSI core allows local users to leave I/O through a SCSI host stuck after command errors. In scsi_dec_host_busy(), clearing SCMD_STATE_INFLIGHT can be observed after host-busy reads, while scsi_eh_inc_host_failed() counts busy commands before incrementing host_failed. When final failed and completed commands race, neither CPU wakes the error-handler task, so the host error state cannot advance and affected storage I/O remains hung.

The record

CVE
CVE-2026-23110
Published
Feb 4, 2026
Updated
Feb 4, 2026
Vendor
The Linux Kernel Organization
Product
Linux Kernel
Classifications
CWE-362, T1499
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Feb 4, 2026CVE publishedPublication date reported by the CVE source.
  2. Feb 4, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=5.5
  2. Affected versionversion=6eb045e092efefafc6687409a6fa6d1dabf0fb69 <219f009ebfd1ef3970888ee9eef4c8a06357f862
  3. Affected versionversion=6eb045e092efefafc6687409a6fa6d1dabf0fb69 <64ae21b9c4f0c7e60cf47a53fa7ab68852079ef0
  4. Affected versionversion=6eb045e092efefafc6687409a6fa6d1dabf0fb69 <9fdc6f28d5e81350ab1d2cac8389062bd09e61e1
  5. Affected versionversion=6eb045e092efefafc6687409a6fa6d1dabf0fb69 <fe2f8ad6f0999db3b318359a01ee0108c703a8c3

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linux Kernelversion=5.5; version=6eb045e092efefafc6687409a6fa6d1dabf0fb69 <219f009ebfd1ef3970888ee9eef4c8a06357f862; version=6eb045e092efefafc6687409a6fa6d1dabf0fb69 <64ae21b9c4f0c7e60cf47a53fa7ab68852079ef0; version=6eb045e092efefafc6687409a6fa6d1dabf0fb69 <9fdc6f28d5e81350ab1d2cac8389062bd09e61e1; version=6eb045e092efefafc6687409a6fa6d1dabf0fb69 <fe2f8ad6f0999db3b318359a01ee0108c703a8c3

Published CVSS scores

4.7NIST NVDCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo