Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-23110scsi: core: Wake up the error handler when final completions race against each other

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.

Timeline

  1. ID reserved

    By Linux

  2. · 22 days later

    Published

  3. · 9 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-23110, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.11% · top 99% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.7.

Affected products

  • Linux · Linux

    • affected 6eb045e092efefafc6687409a6fa6d1dabf0fb69 – < cc872e35c0df80062abc71268d690a2f749e542e
    • affected 6eb045e092efefafc6687409a6fa6d1dabf0fb69 – < 6d9a367be356101963c249ebf10ea10b32886607
    • affected 6eb045e092efefafc6687409a6fa6d1dabf0fb69 – < 9fdc6f28d5e81350ab1d2cac8389062bd09e61e1
    • affected 6eb045e092efefafc6687409a6fa6d1dabf0fb69 – < 64ae21b9c4f0c7e60cf47a53fa7ab68852079ef0
    • affected 6eb045e092efefafc6687409a6fa6d1dabf0fb69 – < 219f009ebfd1ef3970888ee9eef4c8a06357f862
    • affected 6eb045e092efefafc6687409a6fa6d1dabf0fb69 – < fe2f8ad6f0999db3b318359a01ee0108c703a8c3
  • Linux · Linux

    • affected 5.5
    • unaffected < 5.5
    • unaffected 5.10.249 – ≤ 5.10.*
    • unaffected 6.1.162 – ≤ 6.1.*
    • unaffected 6.6.122 – ≤ 6.6.*
    • unaffected 6.12.68 – ≤ 6.12.*
    • unaffected 6.18.8 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-23110 badge
[![CVE-2026-23110](https://cveledger.app/badge/CVE-2026-23110.svg)](https://cveledger.app/cve/CVE-2026-23110)

Record last updated .