# CVE-2026-68396: scsi: core: wake eh reliably when using scsi_schedule_eh

> A race condition in the Linux kernel SCSI core can prevent the error handler from waking, potentially causing a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-94823, BELL-CVE-2026-68396, DEBIAN-CVE-2026-68396, GHSA-g3vc-2pr6-9v45, UBUNTU-CVE-2026-68396

## What is CVE-2026-68396?

CVE-2026-68396 is a vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-68396?


## How do I fix CVE-2026-68396?

Apply the vendor's patch.

## Is CVE-2026-68396 being exploited?

There is no known exploitation of CVE-2026-68396 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68396 and fix it if it is affected.

What it is: CVE-2026-68396 is a vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-68396 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68396/ (Markdown: https://insights.sbomify.com/CVE-2026-68396/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68396
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68396
- OSV: https://osv.dev/vulnerability/CVE-2026-68396

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68396/
Summaries are generated and may contain mistakes; the official description above is the record.