{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.1.5-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  crypto: ccp/sev-dev-tsm - bail out early when pdev-\u003ebus is NULL  dsm_create() initially checks pdev-\u003ebus when computing segment_id:  \tu8 segment_id = pdev-\u003ebus ? pci_domain_nr(pdev-\u003ebus) : 0;  But the next two lines unconditionally dereference pdev-\u003ebus via pcie_find_root_port() and especially pci_dev_id(pdev), which expands to PCI_DEVID(dev-\u003ebus-\u003enumber, dev-\u003edevfn). If pdev-\u003ebus is in fact NULL, segment_id is initialised to 0 but the very next statement crashes the kernel.  smatch flags this:    drivers/crypto/ccp/sev-dev-tsm.c:253 dsm_create() error: we     previously assumed 'pdev-\u003ebus' could be null (see line 251)  Make the NULL handling consistent: if pdev-\u003ebus is NULL the device has no PCI context to work with and SEV TIO setup cannot proceed, so return -ENODEV before any of the bus-dependent lookups. The remaining initialisation now runs only on the path where pdev-\u003ebus is known to be valid.  No change for callers where pdev-\u003ebus is non-NULL, which is the only case where dsm_create() did meaningful work before this change.",
  "id": "DEBIAN-CVE-2026-80651",
  "modified": "2026-09-14T16:47:41.456335433Z",
  "published": "2026-08-28T08:16:50.110Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-80651"
    }
  ],
  "upstream": [
    "CVE-2026-80651"
  ]
}