CVE-2026-43211

PCI: Fix pci_slot_trylock() error handling

HIGH
7.8
CVSS Score
Published: May 6, 2026 at 11:28 AM UTC
Updated: October 19, 2026 at 08:18 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

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/[email protected]]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.19.322 ≤ v < 4.205.10.226 ≤ v < 5.10.2525.15.167 ≤ v < 5.15.2025.4.284 ≤ v < 5.56.1.110 ≤ v < 6.1.1656.10.10 ≤ v < 6.12.756.13 ≤ v < 6.18.166.19 ≤ v < 6.19.66.6.51 ≤ v < 6.6.1284.19.3224e85a3285b0e5c5af6fd2c0fd6e95ffecc19455.10.2265.15.1675.4.2846.1.1106.10.106.116.6.517253b4fed46471cc247c6cacefac890a8472c08378c6e39fef5c428960aff742149bba302dd46f5a790b89c7e911003b8c50ae50e3ac7645de1fae981c68e218ab883dfa368460a59b674084c0240daa4e772898f8bf2e7e1cf661a12c60a5612c4afabdf77a678c33871a6e4ac5b54a71662f1d702335be2355d513b89a2cb511b4ded0deb426cdb01acd0
Vendor states this is fixed in 0425aaf20b407d2f2cf3bf469808e4a35f9abb8b (fixed)
Vendor states this is fixed in 8b08ea9690b212b7bf7f12414039259cf34b1aa0 (fixed)
Vendor states this is fixed in 9368d1ee62829b08aa31836b3ca003803caf0b72 (fixed)
Vendor states this is fixed in 943ed56606a7ab2fe5a99cad572dd17d484310c7 (fixed)
Vendor states this is fixed in a19b61fdb958ffadbba85b43c991eb9fc70c1c1c (fixed)
Vendor states this is fixed in bd435f4b738130d732ef64e0e57e45185f77165d (fixed)
Vendor states this is fixed in ebb27b7399ab8b9eb1f792b329aa5f6250c590d4 (fixed)
Vendor states this is fixed in fbe06a3058114bf95a17a4941b205f4b321c6f0a (fixed)
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.252 (unaffected)
Vendor states this is fixed in 5.15.202 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.165 (unaffected)
Vendor states this is fixed in 6.11 (unaffected)
Vendor states this is fixed in 6.12.75 (unaffected)
Vendor states this is fixed in 6.18.16 (unaffected)
Vendor states this is fixed in 6.19.6 (unaffected)
Vendor states this is fixed in 6.6.128 (unaffected)
Vendor states this is fixed in 7.0 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-667

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card