← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-43211

Last refreshed2026-10-17

Status: UPDATED  |  Advisory ID: CVE-2026-43211

Key Details

CVECVE-2026-43211
CVSS Score / Version
7.8 (High) / CVSS v3.1
Updated2026-10-16
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS Prose
attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products
Linux Kernel
Classified as
CWE-667 (Improper Locking)

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

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]] (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-43211
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-43211
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.