CVE-2026-68396
scsi: 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.
INFO
Published Date :
Aug. 10, 2026, 1:20 p.m.
Last Modified :
Aug. 10, 2026, 1:20 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-68396
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Apply the patch for scsi: core: wake eh reliably.
- Update the Linux kernel to the latest stable version.
- Ensure RCU is correctly configured and operational.
- Test error handling functionality after update.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-68396.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-68396 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-68396
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-68396 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-68396 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Aug. 10, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '6eb045e092efefafc6687409a6fa6d1dabf0fb69', 'lessThan': '866efe8ae8b8b4d095501001b026e1022734be28', 'versionType': 'git'}, {'status': 'affected', 'version': '6eb045e092efefafc6687409a6fa6d1dabf0fb69', 'lessThan': 'c7a15091237205770bd9bd4d14eb1f3029d97a34', 'versionType': 'git'}, {'status': 'affected', 'version': '6eb045e092efefafc6687409a6fa6d1dabf0fb69', 'lessThan': '24d7abda6a2a19e113334accc10029f6a4b57257', 'versionType': 'git'}, {'status': 'affected', 'version': '6eb045e092efefafc6687409a6fa6d1dabf0fb69', 'lessThan': 'dccf3b1798b70f94e958b3d00b83010399e6fb05', 'versionType': 'git'}], 'programFiles': ['drivers/scsi/hosts.c', 'drivers/scsi/scsi_error.c', 'drivers/scsi/scsi_priv.h', 'include/scsi/scsi_host.h'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '5.5'}, {'status': 'unaffected', 'version': '0', 'lessThan': '5.5', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.12.101', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.42', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.6', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc4', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/scsi/hosts.c', 'drivers/scsi/scsi_error.c', 'drivers/scsi/scsi_priv.h', 'include/scsi/scsi_host.h'], 'defaultStatus': 'affected'}] Added 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. Added Reference https://git.kernel.org/stable/c/24d7abda6a2a19e113334accc10029f6a4b57257 Added Reference https://git.kernel.org/stable/c/866efe8ae8b8b4d095501001b026e1022734be28 Added Reference https://git.kernel.org/stable/c/c7a15091237205770bd9bd4d14eb1f3029d97a34 Added Reference https://git.kernel.org/stable/c/dccf3b1798b70f94e958b3d00b83010399e6fb05