{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.1.10-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  scsi: core: pair EH runtime PM get and put  shost-\u003eeh_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-\u003eeh_noresume while the SCSI EH thread is still running.  The problem flow looks like this: PM path   ufshcd_set_dev_pwr_mode()     shost-\u003eeh_noresume = 1     ufshcd_execute_start_stop  \u003c-- trigger EH     ...     shost-\u003eeh_noresume = 0  EH path   scsi_error_handler()     if (!shost-\u003eeh_noresume)       scsi_autopm_get_host()  \u003c-- skipped     ...     if (!shost-\u003eeh_noresume)        scsi_autopm_put_host()  \u003c-- 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.",
  "id": "DEBIAN-CVE-2026-74754",
  "modified": "2026-09-14T16:47:39.758108189Z",
  "published": "2026-08-26T15:16:54.500Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-74754"
    }
  ],
  "upstream": [
    "CVE-2026-74754"
  ]
}