Menu

Star on GitHub · 3.2k

CVE-2026-43211

7.8 · HIGH

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…

Published May 6, 2026CWE-667EPSS 0.14%

Overview

CVE-2026-43211 is a high-severity vulnerability. It was published on May 6, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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_de

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-43211?

CVE-2026-43211 is a high-severity vulnerability. It was published on May 6, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-43211?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-43211?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-43211?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-43211 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all