CVE-2026-43211
Last modified
CVE-2026-43211 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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. EPSS estimates a 0.11% chance of exploitation in the next 30 days.
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/20260116184150.3013258-1-kbusch@meta.com]
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 4.19.322, < 4.20 |
| Linux | Linux Kernel | >= 5.4.284, < 5.5 |
| Linux | Linux Kernel | >= 5.10.226, < 5.10.252 |
| Linux | Linux Kernel | >= 5.15.167, < 5.15.202 |
| Linux | Linux Kernel | >= 6.1.110, < 6.1.165 |
| Linux | Linux Kernel | >= 6.6.51, < 6.6.128 |
| Linux | Linux Kernel | >= 6.10.10, < 6.12.75 |
| Linux | Linux Kernel | >= 6.13, < 6.18.16 |
| Linux | Linux Kernel | >= 6.19, < 6.19.6 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-43211?
How severe is CVE-2026-43211?
How do I fix CVE-2026-43211?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-43206In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-43207In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-43208In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-43209In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-4321Improper neutralization of special elements used in an SQL c…9.8
- CVE-2026-43210In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43212In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-43213In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-43214In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-43215In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-43216In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43217In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-43211?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
