CVE-2026-68396: scsi: core: wake eh reliably when using scsi_schedule_eh
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Fixed version: Linux Linux 24d7abda6a2a19e113334accc10029f6a4b57257, 4827c824a203eea2c0aa5bfdb13d5c5038cc84da, 866efe8ae8b8b4d095501001b026e1022734be28; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 24d7abda6a2a19e113334accc10029f6a4b57257, 4827c824a203eea2c0aa5bfdb13d5c5038cc84da, 866efe8ae8b8b4d095501001b026e1022734be28; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 10, 2026
- Updated
- Oct 21, 2026
- EPSS
- 0.2% · 9th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.5affected
- 6eb045e092efefafc6687409a6fa6d1dabf0fb69 and later · before 4827c824a203eea2c0aa5bfdb13d5c5038cc84daaffected · git
- 6eb045e092efefafc6687409a6fa6d1dabf0fb69 and later · before 866efe8ae8b8b4d095501001b026e1022734be28affected · git
- 6eb045e092efefafc6687409a6fa6d1dabf0fb69 and later · before c7a15091237205770bd9bd4d14eb1f3029d97a34affected · git
- 6eb045e092efefafc6687409a6fa6d1dabf0fb69 and later · before 24d7abda6a2a19e113334accc10029f6a4b57257affected · git
- 6eb045e092efefafc6687409a6fa6d1dabf0fb69 and later · before dccf3b1798b70f94e958b3d00b83010399e6fb05affected · git
- before 5.5not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
- 6.12.101 and later · up to and including 6.12.*not affected · semver
- 6.18.42 and later · up to and including 6.18.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:12 | linux-6.12 | before 6.12.101-1~deb12u1 | 6.12.101-1~deb12u1 |
| Debian:13 | linux | before 6.12.101-1 | 6.12.101-1 |
| Debian:14 | linux | before 7.1.6-1 | 7.1.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-68393Aug 10, 2026 · Bluetooth: hci_sync: extend conn_hash lookup critical sections35Monitor
- ← EarlierCVE-2026-68394Aug 10, 2026 · Bluetooth: MGMT: revalidate LOAD_CONN_PARAM queued update31Monitor
- Later →CVE-2026-68397Aug 10, 2026 · net/iucv: take a reference on the socket found in afiucv_hs_rcv()35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 24d7abda6a2a19e113334accc10029f6a4b57257 | Vendor (CNA) |
| Linux Linux | 4827c824a203eea2c0aa5bfdb13d5c5038cc84da | Vendor (CNA) |
| Linux Linux | 866efe8ae8b8b4d095501001b026e1022734be28 | Vendor (CNA) |
| Linux Linux | c7a15091237205770bd9bd4d14eb1f3029d97a34 | Vendor (CNA) |
| Linux Linux | dccf3b1798b70f94e958b3d00b83010399e6fb05 | Vendor (CNA) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.101-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.