CVE-2026-43211CWE-667

CVE-2026-43211

High · published May 6, 2026

CVSS v3.1
7.8
EPSS
0%
Percentile
2.7
In the wild
Unconfirmed
What it is

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]]

The record
Technical detail
CVSS v3.1
7.8 · HIGH
Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS v4.0
Not supplied
EPSS
0.00136 · 2.7th percentile
Weakness
CWE-667 · Improper Locking
Published
2026-05-06T16:16Z
Affected products (9)
ProductVersionsFixed in
linux/linux_kernel≥ 4.19.322, < 4.204.20
linux/linux_kernel≥ 5.4.284, < 5.55.5
linux/linux_kernel≥ 5.10.226, < 5.10.2525.10.252
linux/linux_kernel≥ 5.15.167, < 5.15.2025.15.202
linux/linux_kernel≥ 6.1.110, < 6.1.1656.1.165
linux/linux_kernel≥ 6.6.51, < 6.6.1286.6.128
linux/linux_kernel≥ 6.10.10, < 6.12.756.12.75
linux/linux_kernel≥ 6.13, < 6.18.166.18.16
linux/linux_kernel≥ 6.19, < 6.19.66.19.6
References (8)
EPSS history
Timeline
  • 06 MAY 11:28Z
    PCI: Fix pci_slot_trylock() error handling
    cvelistv5