CVE-2026-43211: PCI: Fix pci_slot_trylock() error handling
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]
Metrics
- CVSS v3.1
- 7.8
- Severity
- HIGH
- Fixed in
- 0
- Affected Products
- 2
Fix available
- Linux / Linux< ebb27b7399ab8b9eb1f792b329aa5f6250c590d4 (from e2355d513b89a2cb511b4ded0deb426cdb01acd0) · < fbe06a3058114bf95a17a4941b205f4b321c6f0a (from 04e85a3285b0e5c5af6fd2c0fd6e95ffecc01945) · < 943ed56606a7ab2fe5a99cad572dd17d484310c7 (from 7253b4fed46471cc247c6cacefac890a8472c083) · < a19b61fdb958ffadbba85b43c991eb9fc70c1c1c (from 78c6e39fef5c428960aff742149bba302dd46f5a) · < 0425aaf20b407d2f2cf3bf469808e4a35f9abb8b (from a4e772898f8bf2e7e1cf661a12c60a5612c4afab) · < bd435f4b738130d732ef64e0e57e45185f77165d (from a4e772898f8bf2e7e1cf661a12c60a5612c4afab)
- Linux / Linux6.11Fixed in 0, 5.10.252, 5.15.202, 6.1.165, 6.6.128, 6.12.75, 6.18.16, 6.19.6, 7.0
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H