Privileged PCI lock corruption via unmatched unlock
Published May 6, 2026 · Updated May 6, 2026
Improper lock handling in the PCI subsystem of Linux Kernel allows local users to corrupt PCI bridge lock state. On pci_bus_trylock() failure, pci_slot_trylock() calls pci_dev_unlock() although that path no longer acquired the bridge-device lock, releasing a lock held by another thread. Reachability requires CAP_SYS_ADMIN in the initial user namespace or equivalent privileged VFIO access; outcomes are a lock warning or an incorrect cross-thread unlock.
Summary
What happened
Improper lock handling in the PCI subsystem of Linux Kernel allows local users to corrupt PCI bridge lock state. On pci_bus_trylock() failure, pci_slot_trylock() calls pci_dev_unlock() although that path no longer acquired the bridge-device lock, releasing a lock held by another thread. Reachability requires CAP_SYS_ADMIN in the initial user namespace or equivalent privileged VFIO access; outcomes are a lock warning or an incorrect cross-thread unlock.
The record
- CVE
- CVE-2026-43211
- Published
- May 6, 2026
- Updated
- May 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 6, 2026CVE publishedPublication date reported by the CVE source.
- May 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=04e85a3285b0e5c5af6fd2c0fd6e95ffecc01945 <fbe06a3058114bf95a17a4941b205f4b321c6f0a
- Affected versionversion=0790b89c7e911003b8c50ae50e3ac7645de1fae9
- Affected versionversion=6.11
- Affected versionversion=7253b4fed46471cc247c6cacefac890a8472c083 <943ed56606a7ab2fe5a99cad572dd17d484310c7
- Affected versionversion=78c6e39fef5c428960aff742149bba302dd46f5a <a19b61fdb958ffadbba85b43c991eb9fc70c1c1c
- Affected versionversion=81c68e218ab883dfa368460a59b674084c0240da
- Affected versionversion=a4e772898f8bf2e7e1cf661a12c60a5612c4afab <0425aaf20b407d2f2cf3bf469808e4a35f9abb8b
- Affected versionversion=a4e772898f8bf2e7e1cf661a12c60a5612c4afab <8b08ea9690b212b7bf7f12414039259cf34b1aa0
- Affected versionversion=a4e772898f8bf2e7e1cf661a12c60a5612c4afab <9368d1ee62829b08aa31836b3ca003803caf0b72
- Affected versionversion=a4e772898f8bf2e7e1cf661a12c60a5612c4afab <bd435f4b738130d732ef64e0e57e45185f77165d
- Affected versionversion=df77a678c33871a6e4ac5b54a71662f1d702335b
- Affected versionversion=e2355d513b89a2cb511b4ded0deb426cdb01acd0 <ebb27b7399ab8b9eb1f792b329aa5f6250c590d4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo