Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 2 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected ae0751ffc77e7f21629970fdab5528c573e637f8 – < 9aca00c74730f4bc12d0717d33db637a16ccdfea
    • affected ae0751ffc77e7f21629970fdab5528c573e637f8 – < 1ec5f6aa38ea990af37c49af7a4bb3db00da7f9d
    • affected ae0751ffc77e7f21629970fdab5528c573e637f8 – < 0038a2a75a15d163f428c93103c6d02d4d231a7a
    • affected ae0751ffc77e7f21629970fdab5528c573e637f8 – < fdc93f4a801077efbf1b87570ade8d8f325de62f
    • affected ae0751ffc77e7f21629970fdab5528c573e637f8 – < e83eed1bea142c8fe852fd53156845b88252ecd8
    • affected ae0751ffc77e7f21629970fdab5528c573e637f8 – < 872f486259ae0bc6b73ca4735a15d013241f73e9
  • Linux · Linux

    • affected 3.3
    • unaffected < 3.3
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.1.10 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-74754 badge
[![CVE-2026-74754](https://cveledger.app/badge/CVE-2026-74754.svg)](https://cveledger.app/cve/CVE-2026-74754)

Record last updated .