CVE-2026-43211 — PCI: Fix pci_slot_trylock() error handling
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]
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.1% (30-day exploitation probability)+0
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ a4e772898f8bf2e7e1cf661a12c60a5612c4afab and < bd435f4b738130d732ef64e0e57e45185f77165dversion 6.11≥ 6.10.10 and < 6.11≥ 5.4.284 and < 5.5≥ 4.19.322 and < 4.20≥ 6.6.51 and < 6.6.128≥ 6.1.110 and < 6.1.165≥ 5.15.167 and < 5.15.202 and 11 more≥ 5.10.226 and < 5.10.252version 81c68e218ab883dfa368460a59b674084c0240daversion df77a678c33871a6e4ac5b54a71662f1d702335bversion 0790b89c7e911003b8c50ae50e3ac7645de1fae9≥ a4e772898f8bf2e7e1cf661a12c60a5612c4afab and < 9368d1ee62829b08aa31836b3ca003803caf0b72≥ a4e772898f8bf2e7e1cf661a12c60a5612c4afab and < 8b08ea9690b212b7bf7f12414039259cf34b1aa0≥ a4e772898f8bf2e7e1cf661a12c60a5612c4afab and < 0425aaf20b407d2f2cf3bf469808e4a35f9abb8b≥ 78c6e39fef5c428960aff742149bba302dd46f5a and < a19b61fdb958ffadbba85b43c991eb9fc70c1c1c≥ 7253b4fed46471cc247c6cacefac890a8472c083 and < 943ed56606a7ab2fe5a99cad572dd17d484310c7≥ 04e85a3285b0e5c5af6fd2c0fd6e95ffecc01945 and < fbe06a3058114bf95a17a4941b205f4b321c6f0a≥ e2355d513b89a2cb511b4ded0deb426cdb01acd0 and < ebb27b7399ab8b9eb1f792b329aa5f6250c590d4 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel |
≥ 4.19.322 and < 4.20≥ 6.19 and < 6.19.6≥ 6.13 and < 6.18.16≥ 6.10.10 and < 6.12.75≥ 6.6.51 and < 6.6.128≥ 6.1.110 and < 6.1.165≥ 5.15.167 and < 5.15.202≥ 5.10.226 and < 5.10.252 and 1 more≥ 5.4.284 and < 5.5 |
Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 0.14%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- Fix documented
- CVSS changed · 7.8
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
8 on the record
- git.kernel.org/stable/c/8b08ea9690b212b7bf7f12414039259cf34b1aa0
- git.kernel.org/stable/c/bd435f4b738130d732ef64e0e57e45185f77165d
- git.kernel.org/stable/c/a19b61fdb958ffadbba85b43c991eb9fc70c1c1c
- git.kernel.org/stable/c/943ed56606a7ab2fe5a99cad572dd17d484310c7
- git.kernel.org/stable/c/9368d1ee62829b08aa31836b3ca003803caf0b72
- git.kernel.org/stable/c/0425aaf20b407d2f2cf3bf469808e4a35f9abb8b
- git.kernel.org/stable/c/ebb27b7399ab8b9eb1f792b329aa5f6250c590d4
- git.kernel.org/stable/c/fbe06a3058114bf95a17a4941b205f4b321c6f0a
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 17h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 17h
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-43211 is "PCI: Fix pci_slot_trylock() error handling", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 0.14% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.