Skip to main content
VulnerabilityPublished Updated

CVE-2026-74754: Linux kernel · scsi: core: pair EH runtime PM get and put

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in fdc93f4a801077efbf1b87570ade8d8f325de62f : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in fdc93f4a801077efbf1b87570ade8d8f325de62f, e83eed1bea142c8fe852fd53156845b88252ecd8, 872f486259ae0bc6b73ca4735a15d013241f73e9 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ ae0751ffc77e7f21629970fdab5528c573e637f8, < fdc93f4a801077efbf1b87570ade8d8f325de62f
Fixed in
  • fdc93f4a801077efbf1b87570ade8d8f325de62f
LinuxLinuxAffected
  • ≥ ae0751ffc77e7f21629970fdab5528c573e637f8, < e83eed1bea142c8fe852fd53156845b88252ecd8
Fixed in
  • e83eed1bea142c8fe852fd53156845b88252ecd8
LinuxLinuxAffected
  • ≥ ae0751ffc77e7f21629970fdab5528c573e637f8, < 872f486259ae0bc6b73ca4735a15d013241f73e9
Fixed in
  • 872f486259ae0bc6b73ca4735a15d013241f73e9
LinuxLinuxAffected
  • ≥ ae0751ffc77e7f21629970fdab5528c573e637f8, < 0038a2a75a15d163f428c93103c6d02d4d231a7a
Fixed in
  • 0038a2a75a15d163f428c93103c6d02d4d231a7a
LinuxLinuxAffected
  • ≥ ae0751ffc77e7f21629970fdab5528c573e637f8, < 1ec5f6aa38ea990af37c49af7a4bb3db00da7f9d
Fixed in
  • 1ec5f6aa38ea990af37c49af7a4bb3db00da7f9d
LinuxLinuxAffected
  • =3.3
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: core: pair EH runtime PM get and put shost->eh_noresume is currently consulted twice in one error handling iteration: once before scsi_autopm_get_host() and once again before scsi_autopm_put_host(). That is racy when a PM-triggered error path flips shost->eh_noresume while the SCSI EH thread is still running. The problem flow looks like this: PM path ufshcd_set_dev_pwr_mode() shost->eh_noresume = 1 ufshcd_execute_start_stop <-- trigger EH ... shost->eh_noresume = 0 EH path scsi_error_handler() if (!shost->eh_noresume) scsi_autopm_get_host() <-- skipped ... if (!shost->eh_noresume) scsi_autopm_put_host() <-- executed later In that case one EH iteration can skip autoresume on entry and still drop a runtime PM reference on exit. That leaves an unmatched runtime PM put and can trigger a runtime PM usage count underflow. Fix this by making eh_noresume a regular bool so it can be accessed with READ_ONCE() and WRITE_ONCE(). Snapshot it once per EH iteration and use that snapshot for both runtime PM get and put decisions.

References

Community reviews

Loading reviews…