CVE-2026-43211

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-06. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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:

  • A warning that the lock is being unlocked when no one holds it.
  • 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]]

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
1.3%
KEV
Not listed

Published

May 6, 2026

Last Modified

May 11, 2026

Advisory Details (8)

Auto-updated May 11, 2026
No patch confirmed yet.
generic

PCI: Fix pci_slot_trylock() error handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fbe06a3058114bf95a17a4941b205f4b321c6f0a
generic

PCI: Fix pci_slot_trylock() error handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ebb27b7399ab8b9eb1f792b329aa5f6250c590d4
generic

PCI: Fix pci_slot_trylock() error handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bd435f4b738130d732ef64e0e57e45185f77165d
generic

PCI: Fix pci_slot_trylock() error handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a19b61fdb958ffadbba85b43c991eb9fc70c1c1c
generic

PCI: Fix pci_slot_trylock() error handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/943ed56606a7ab2fe5a99cad572dd17d484310c7
generic

PCI: Fix pci_slot_trylock() error handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9368d1ee62829b08aa31836b3ca003803caf0b72
generic

PCI: Fix pci_slot_trylock() error handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8b08ea9690b212b7bf7f12414039259cf34b1aa0
generic

PCI: Fix pci_slot_trylock() error handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0425aaf20b407d2f2cf3bf469808e4a35f9abb8b

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.252osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-24 14:17 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:14 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:24 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-20 08:32 UTCOSV refresh
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-16 17:03 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-13 22:30 UTCEPSS rescore
  12. 2026-07-12 05:46 UTCEPSS rescore
  13. 2026-07-09 19:10 UTCEPSS rescore
  14. 2026-07-08 15:16 UTCEPSS rescore
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-06 02:23 UTCEPSS rescore
  17. 2026-07-05 02:30 UTCEPSS rescore
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-01 15:06 UTCEPSS rescore
  20. 2026-06-30 23:22 UTCEPSS rescore
  21. 2026-06-28 14:07 UTCEPSS rescore
  22. 2026-06-28 04:56 UTCEPSS rescore
  23. 2026-06-27 03:08 UTCEPSS rescore
  24. 2026-06-24 14:05 UTCEPSS rescore
  25. 2026-06-23 21:33 UTCEPSS rescore
Show 71 more
  1. 2026-06-22 14:25 UTCEPSS rescore
  2. 2026-06-22 14:25 UTCEPSS rescore
  3. 2026-06-18 17:52 UTCEPSS rescore
  4. 2026-06-18 17:52 UTCEPSS rescore
  5. 2026-06-17 17:53 UTCEPSS rescore
  6. 2026-06-16 17:52 UTCEPSS rescore
  7. 2026-06-15 17:49 UTCEPSS rescore
  8. 2026-06-14 19:57 UTCGHSA enrichment
  9. 2026-06-14 07:36 UTCGHSA enrichment
  10. 2026-06-13 23:00 UTCEPSS rescore
  11. 2026-06-13 00:00 UTCGHSA enrichment
  12. 2026-06-12 23:12 UTCEPSS rescore
  13. 2026-06-12 23:12 UTCEPSS rescore
  14. 2026-06-12 02:30 UTCGHSA enrichment
  15. 2026-06-11 14:08 UTCGHSA enrichment
  16. 2026-06-11 14:00 UTCEPSS rescore
  17. 2026-06-11 01:46 UTCGHSA enrichment
  18. 2026-06-10 22:18 UTCEPSS rescore
  19. 2026-06-10 13:22 UTCEPSS rescore
  20. 2026-06-10 13:22 UTCEPSS rescore
  21. 2026-06-10 11:25 UTCGHSA enrichment
  22. 2026-06-09 23:03 UTCGHSA enrichment
  23. 2026-06-09 10:36 UTCGHSA enrichment
  24. 2026-06-08 22:14 UTCGHSA enrichment
  25. 2026-06-08 14:17 UTCEPSS rescore
  26. 2026-06-08 14:17 UTCEPSS rescore
  27. 2026-06-08 03:35 UTCGHSA enrichment
  28. 2026-06-07 15:25 UTCEPSS rescore
  29. 2026-06-07 15:25 UTCEPSS rescore
  30. 2026-06-07 15:13 UTCGHSA enrichment
  31. 2026-06-07 02:51 UTCGHSA enrichment
  32. 2026-06-06 14:29 UTCGHSA enrichment
  33. 2026-06-06 13:47 UTCEPSS rescore
  34. 2026-06-06 13:47 UTCEPSS rescore
  35. 2026-06-06 02:06 UTCGHSA enrichment
  36. 2026-06-05 22:47 UTCEPSS rescore
  37. 2026-06-05 13:26 UTCGHSA enrichment
  38. 2026-06-05 06:10 UTCEPSS rescore
  39. 2026-06-05 06:10 UTCEPSS rescore
  40. 2026-06-05 01:04 UTCGHSA enrichment
  41. 2026-06-04 13:12 UTCEPSS rescore
  42. 2026-06-04 13:12 UTCEPSS rescore
  43. 2026-06-04 11:45 UTCGHSA enrichment
  44. 2026-06-03 23:23 UTCGHSA enrichment
  45. 2026-06-03 11:01 UTCGHSA enrichment
  46. 2026-06-02 22:39 UTCGHSA enrichment
  47. 2026-06-02 20:13 UTCEPSS rescore
  48. 2026-06-02 10:17 UTCGHSA enrichment
  49. 2026-06-01 21:55 UTCGHSA enrichment
  50. 2026-06-01 13:52 UTCEPSS rescore
  51. 2026-06-01 13:52 UTCEPSS rescore
  52. 2026-06-01 09:33 UTCGHSA enrichment
  53. 2026-05-31 22:30 UTCEPSS rescore
  54. 2026-05-31 22:30 UTCEPSS rescore
  55. 2026-05-31 00:16 UTCEPSS rescore
  56. 2026-05-31 00:16 UTCEPSS rescore
  57. 2026-05-29 13:44 UTCEPSS rescore
  58. 2026-05-29 13:44 UTCEPSS rescore
  59. 2026-05-28 13:44 UTCEPSS rescore
  60. 2026-05-28 13:44 UTCEPSS rescore
  61. 2026-05-27 13:40 UTCEPSS rescore
  62. 2026-05-27 13:40 UTCEPSS rescore
  63. 2026-05-26 13:44 UTCEPSS rescore
  64. 2026-05-26 07:18 UTCEPSS rescore
  65. 2026-05-21 22:43 UTCEPSS rescore
  66. 2026-05-20 22:38 UTCEPSS rescore
  67. 2026-05-20 22:38 UTCEPSS rescore
  68. 2026-05-20 14:14 UTCEG score recompute
  69. 2026-05-20 14:14 UTCGHSA enrichment
  70. 2026-05-20 11:22 UTCEPSS rescore
  71. 2026-05-20 11:22 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-43211?
CVE-2026-43211 is a high vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: PCI: Fix pcislottrylock() error handling Commit a4e772898f8b ("PCI: Add missing bridge lock to pcibuslock()") delegates the bridge device's pcidevtrylock() to pcibustrylock() in pcislottrylock(), but it forgets to remove the…
When was CVE-2026-43211 disclosed?
CVE-2026-43211 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on May 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43211 actively exploited?
CVE-2026-43211 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43211?
CVE-2026-43211 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43211?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43211, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-43211

Explore →

Is Your Infrastructure Affected by CVE-2026-43211?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.