{
  "affected": [
    {
      "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"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  phy: qcom: qmp-usb: Fix possible NULL-deref on early runtime suspend  There is a small window where the runtime suspend callback may run after pm_runtime_enable() and before pm_runtime_forbid(). In this case, a crash occurs because runtime suspend/resume dereferences qmp-\u003ephy pointer, which is not yet initialized:         `if (!qmp-\u003ephy-\u003einit_count) {`  This can also happen if user re-enables runtime-pm via the sysfs attribute before qmp phy is initialized.  Similarly to other qcom phy drivers, introduce a qmp-\u003ephy_initialized variable that can be used to avoid relying on the possibly uninitialized phy pointer.",
  "id": "DEBIAN-CVE-2026-90280",
  "modified": "2026-09-18T04:47:26.349292887Z",
  "published": "2026-09-17T17:17:24.690Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-90280"
    }
  ],
  "upstream": [
    "CVE-2026-90280"
  ]
}