CVE-2026-43211PCI: Fix pci_slot_trylock() error handling
Updated under an hour ago ()
Does this affect you?
It affects Linux and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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]
- CVSS
- 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Analyzed
- Record last updated
- Oct 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from e2355d513b89a2cb511b4ded0deb426cdb01acd0 before ebb27b7399ab8b9eb1f792b329aa5f6250c590d4; from 04e85a3285b0e5c5af6fd2c0fd6e95ffecc01945 before fbe06a3058114bf95a17a4941b205f4b321c6f0a; 7253b4fed46471cc247c6cacefac890a8472c083 builds before 943ed56606a7ab2fe5a99cad572dd17d484310c7; from 78c6e39fef5c428960aff742149bba302dd46f5a before a19b61fdb958ffadbba85b43c991eb9fc70c1c1c; from a4e772898f8bf2e7e1cf661a12c60a5612c4afab before 0425aaf20b407d2f2cf3bf469808e4a35f9abb8b; from a4e772898f8bf2e7e1cf661a12c60a5612c4afab before bd435f4b738130d732ef64e0e57e45185f77165d; from a4e772898f8bf2e7e1cf661a12c60a5612c4afab before 8b08ea9690b212b7bf7f12414039259cf34b1aa0; from a4e772898f8bf2e7e1cf661a12c60a5612c4afab before 9368d1ee62829b08aa31836b3ca003803caf0b72; and 10 more ranges | CNA record |
linux linux_kernel linux:linux_kernel | from 4.19.322 before 4.20; from 5.4.284 before 5.5; from 5.10.226 before 5.10.252; from 5.15.167 before 5.15.202; from 6.1.110 before 6.1.165; from 6.6.51 before 6.6.128; from 6.10.10 before 6.12.75; from 6.13 before 6.18.16; and 1 more ranges | NVD |
References
- https://git.kernel.org/stable/c/ebb27b7399ab8b9eb1f792b329aa5f6250c590d4patch
- https://git.kernel.org/stable/c/fbe06a3058114bf95a17a4941b205f4b321c6f0apatch
- https://git.kernel.org/stable/c/943ed56606a7ab2fe5a99cad572dd17d484310c7patch
- https://git.kernel.org/stable/c/a19b61fdb958ffadbba85b43c991eb9fc70c1c1cpatch
- https://git.kernel.org/stable/c/0425aaf20b407d2f2cf3bf469808e4a35f9abb8bpatch
- https://git.kernel.org/stable/c/bd435f4b738130d732ef64e0e57e45185f77165dpatch
- https://git.kernel.org/stable/c/8b08ea9690b212b7bf7f12414039259cf34b1aa0patch
- https://git.kernel.org/stable/c/9368d1ee62829b08aa31836b3ca003803caf0b72patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.