CVE-2026-74754: Linux kernel · scsi: core: pair EH runtime PM get and put
Source GCVE Database
Not known to be exploited · fixed in fdc93f4a801077efbf1b87570ade8d8f325de62f : update Linux kernel when convenient.
Data as of 30 Oct 2026, 19:33 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in fdc93f4a801077efbf1b87570ade8d8f325de62f, e83eed1bea142c8fe852fd53156845b88252ecd8, 872f486259ae0bc6b73ca4735a15d013241f73e9 +3
Exploitation evidence
Disclosed: evidence found.
CVE published 26 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix has been implemented that changes the eh_noresume flag to a regular boolean accessed atomically and snapshots its value once per error handling iteration. Users should apply the official Linux kernel patch that addresses this race condition to prevent runtime PM usage count underflow. Since this is a kernel-level issue, updating to a patched kernel version is the recommended remediation.
Description
A race condition in the Linux kernel SCSI core error handling can cause a runtime power management (PM) usage count underflow. This occurs because the shost->eh_noresume flag is checked twice during error handling without proper synchronization, leading to an unmatched runtime PM put operation. The issue is fixed by making the flag a regular boolean accessed atomically and snapshotting it once per error handling iteration.
References
- nvd.nist.gov/vuln/detail/CVE-2026-74754 (opens in a new tab)
- git.kernel.org/stable/c/0038a2a75a15d163f428c93103c6d02d4d231a7a (opens in a new tab)
- git.kernel.org/stable/c/1ec5f6aa38ea990af37c49af7a4bb3db00da7f9d (opens in a new tab)
- git.kernel.org/stable/c/872f486259ae0bc6b73ca4735a15d013241f73e9 (opens in a new tab)
- git.kernel.org/stable/c/9aca00c74730f4bc12d0717d33db637a16ccdfea (opens in a new tab)
- git.kernel.org/stable/c/e83eed1bea142c8fe852fd53156845b88252ecd8 (opens in a new tab)
- git.kernel.org/stable/c/fdc93f4a801077efbf1b87570ade8d8f325de62f (opens in a new tab)