GHSA-G3VC-2PR6-9V45
Vulnerability from github – Published: 2026-08-10 15:33 – Updated: 2026-08-10 15:33In 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": [],
"aliases": [
"CVE-2026-68396"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-10T13:20:33Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: core: wake eh reliably when using scsi_schedule_eh\n\nDrivers which use the scsi_schedule_eh function to run the error handler\ncurrently risk the error handler thread never waking once all commands are\ntimed out or inactive. There is no enforced memory order between setting\nthe host into error recovery state and counting busy commands. This can\nresult in a race with scsi_dec_host_busy where neither CPU sees both\nconditions of all commands inactive and the host error state to request\nwaking the error handler.\n\nTo fix this, run the scsi_schedule_eh\u0027s scsi_eh_wakeup from a new work item\nwhich will use rcu to ensure scsi_schedule_eh\u0027s call to scsi_host_busy will\noccur after the error state is globally visible and will be seen by any\ncurrent scsi_dec_host_busy callers.",
"id": "GHSA-g3vc-2pr6-9v45",
"modified": "2026-08-10T15:33:49Z",
"published": "2026-08-10T15:33:49Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-68396"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/24d7abda6a2a19e113334accc10029f6a4b57257"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/866efe8ae8b8b4d095501001b026e1022734be28"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c7a15091237205770bd9bd4d14eb1f3029d97a34"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/dccf3b1798b70f94e958b3d00b83010399e6fb05"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.