{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.1.170-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.85-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.19.6-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  PCI: Fix pci_slot_trylock() error handling  Commit a4e772898f8b (\"PCI: Add missing bridge lock to pci_bus_lock()\") delegates the bridge device's pci_dev_trylock() to pci_bus_trylock() in pci_slot_trylock(), but it forgets to remove the corresponding pci_dev_unlock() when pci_bus_trylock() fails.  Before a4e772898f8b, the code did:    if (!pci_dev_trylock(dev)) /* \u003c- lock bridge device */     goto unlock;   if (dev-\u003esubordinate) {     if (!pci_bus_trylock(dev-\u003esubordinate)) {       pci_dev_unlock(dev);   /* \u003c- unlock bridge device */       goto unlock;     }   }  After a4e772898f8b the bridge-device lock is no longer taken, but the pci_dev_unlock(dev) on the failure path was left in place, leading to the bug.  This yields one of two errors:    1. A warning that the lock is being unlocked when no one holds it.   2. An incorrect unlock of a lock that belongs to another thread.  Fix it by removing the now-redundant pci_dev_unlock(dev) on the failure path.  [Same patch later posted by Keith at https://patch.msgid.link/20260116184150.3013258-1-kbusch@meta.com]",
  "id": "DEBIAN-CVE-2026-43211",
  "modified": "2026-09-14T16:47:42.848467614Z",
  "published": "2026-05-06T12:16:40.527Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-43211"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-43211"
  ]
}