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-68396scsi: core: wake eh reliably when using scsi_schedule_eh

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: core: wake eh reliably when using scsi_schedule_eh Drivers which use the scsi_schedule_eh function to run the error handler currently risk the error handler thread never waking once all commands are timed out or inactive. There is no enforced memory order between setting the host into error recovery state and counting busy commands. This can result in a race with scsi_dec_host_busy where neither CPU sees both conditions of all commands inactive and the host error state to request waking the error handler. To fix this, run the scsi_schedule_eh's scsi_eh_wakeup from a new work item which will use rcu to ensure scsi_schedule_eh's call to scsi_host_busy will occur after the error state is globally visible and will be seen by any current scsi_dec_host_busy callers.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 3 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (14 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: Not scored.

Affected products

  • Linux · Linux

    • affected 6eb045e092efefafc6687409a6fa6d1dabf0fb69 – < d1280822db11c423ad47b43c9d69a5e56199161e
    • affected 6eb045e092efefafc6687409a6fa6d1dabf0fb69 – < 4827c824a203eea2c0aa5bfdb13d5c5038cc84da
    • affected 6eb045e092efefafc6687409a6fa6d1dabf0fb69 – < 866efe8ae8b8b4d095501001b026e1022734be28
    • affected 6eb045e092efefafc6687409a6fa6d1dabf0fb69 – < c7a15091237205770bd9bd4d14eb1f3029d97a34
    • affected 6eb045e092efefafc6687409a6fa6d1dabf0fb69 – < 24d7abda6a2a19e113334accc10029f6a4b57257
    • affected 6eb045e092efefafc6687409a6fa6d1dabf0fb69 – < dccf3b1798b70f94e958b3d00b83010399e6fb05
  • Linux · Linux

    • affected 5.5
    • unaffected < 5.5
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .