CVE-2026-68396

Unknown

Last modified

CVE-2026-68396 is a vulnerability of currently unknown severity. 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.

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 6eb045e092efefafc6687409a6fa6d1dabf0fb69, < 866efe8ae8b8b4d095501001b026e1022734be28; >= 6eb045e092efefafc6687409a6fa6d1dabf0fb69, < c7a15091237205770bd9bd4d14eb1f3029d97a34; >= 6eb045e092efefafc6687409a6fa6d1dabf0fb69, < 24d7abda6a2a19e113334accc10029f6a4b57257; >= 6eb045e092efefafc6687409a6fa6d1dabf0fb69, < dccf3b1798b70f94e958b3d00b83010399e6fb05
LinuxLinux5.5

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-68396?
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.
How severe is CVE-2026-68396?
Severity scoring for CVE-2026-68396 is pending analysis.
How do I fix CVE-2026-68396?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-68396?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST