Linux Kernel up to 6.19.5 PCI pci_slot_trylock privilege escalation

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.3$0-$5k0.00

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.19.5. It has been classified as problematic. Affected is the function pci_slot_trylock of the component PCI. The manipulation leads to an unknown weakness. This vulnerability is referenced as CVE-2026-43211. No exploit is available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Linux Kernel up to 6.19.5. This issue affects the function pci_slot_trylock of the component PCI. The impact remains unknown. The summary by CVE is:

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]]

It is possible to read the advisory at git.kernel.org. The identification of this vulnerability is CVE-2026-43211 since 05/01/2026. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/04/2026).

The vulnerability scanner Nessus provides a plugin with the ID 318589 (Oracle Linux 10 / 9 : Unbreakable Enterprise kernel (ELSA-2026-50293)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.10.252, 5.15.202, 6.1.165, 6.6.128, 6.12.75, 6.18.16 or 6.19.6 eliminates this vulnerability. Applying the patch ebb27b7399ab8b9eb1f792b329aa5f6250c590d4/fbe06a3058114bf95a17a4941b205f4b321c6f0a/943ed56606a7ab2fe5a99cad572dd17d484310c7/a19b61fdb958ffadbba85b43c991eb9fc70c1c1c/0425aaf20b407d2f2cf3bf469808e4a35f9abb8b/bd435f4b738130d732ef64e0e57e45185f77165d/8b08ea9690b212b7bf7f12414039259cf34b1aa0/9368d1ee62829b08aa31836b3ca003803caf0b72 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (318589). Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Privilege escalation
CWE: Unknown
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 318589
Nessus Name: Oracle Linux 10 / 9 : Unbreakable Enterprise kernel (ELSA-2026-50293)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.252/5.15.202/6.1.165/6.6.128/6.12.75/6.18.16/6.19.6
Patch: ebb27b7399ab8b9eb1f792b329aa5f6250c590d4/fbe06a3058114bf95a17a4941b205f4b321c6f0a/943ed56606a7ab2fe5a99cad572dd17d484310c7/a19b61fdb958ffadbba85b43c991eb9fc70c1c1c/0425aaf20b407d2f2cf3bf469808e4a35f9abb8b/bd435f4b738130d732ef64e0e57e45185f77165d/8b08ea9690b212b7bf7f12414039259cf34b1aa0/9368d1ee62829b08aa31836b3ca003803caf0b72

Timelineinfo

05/01/2026 CVE reserved
05/06/2026 +5 days Advisory disclosed
05/06/2026 +0 days VulDB entry created
06/04/2026 +29 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-43211 (🔒)
GCVE (CVE): GCVE-0-2026-43211
GCVE (VulDB): GCVE-100-361415

Entryinfo

Created: 05/06/2026 16:35
Updated: 06/04/2026 14:47
Changes: 05/06/2026 16:35 (57), 06/04/2026 14:47 (2)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to stay up to date on a daily basis?

Enable the mail alert feature now!