cve.bz

CVE-2026-43211 linux linux kernel: Improper Locking

7.8 highEPSS 0.1%Fix available

High (7.8) in linux linux kernel. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
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]

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-667 Improper Locking
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-43211 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-43211?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-43211?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-43211 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linuxfrom 5.10.226 before 5.10.252
Linuxfrom 5.15.167 before 5.15.202
Linuxfrom 6.1.110 before 6.1.165
Linuxfrom 6.6.51 before 6.6.128
Linuxfrom 4.19.322 before 4.20
Linuxfrom 5.4.284 before 5.5
Linuxfrom 6.10.10 before 6.11
Linux6.11 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.252
Linux5.155.15.202
Linux6.16.1.165
Linux6.66.6.128
Linux6.126.12.75
Linux6.186.18.16
Linux6.196.19.6
Linuxlater releases7.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.170-1DEBIAN-CVE-2026-43211
Debian13linux6.12.85-1DEBIAN-CVE-2026-43211
Debian14linux6.19.6-1DEBIAN-CVE-2026-43211
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-43211
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-43211
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-43211
Ubuntu22.04:LTSlinux5.15.0-186.196UBUNTU-CVE-2026-43211 USN-8575-1
Ubuntu22.04:LTSlinux-aws5.15.0-1112.119UBUNTU-CVE-2026-43211 USN-8575-2
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1060.63~22.04.1UBUNTU-CVE-2026-43211 USN-8492-2
Ubuntu22.04:LTSlinux-azure, linux-azure-fde5.15.0-1117.126UBUNTU-CVE-2026-43211 USN-8575-3 USN-8610-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1063.71~22.04.1UBUNTU-CVE-2026-43211 USN-8606-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1062.69~22.04.1UBUNTU-CVE-2026-43211 USN-8609-1
Ubuntu22.04:LTSlinux-gcp5.15.0-1112.122UBUNTU-CVE-2026-43211 USN-8575-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1063.69~22.04.1UBUNTU-CVE-2026-43211 USN-8492-2
Ubuntu22.04:LTSlinux-gke5.15.0-1108.114UBUNTU-CVE-2026-43211 USN-8575-1
65 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 15 SP7, Linux Enterprise Live Patching 15 SP7, Linux Enterprise Module for Legacy 15 SP7 and 1 morekernel-default6.4.0-150700.53.73.2SUSE-SU-2026:3166-1
SUSELinux Enterprise High Availability Extension 16.0kernel-default6.12.0-160000.37.1SUSE-SU-2026:23237-1
SUSELinux Enterprise High Performance Computing 15 SP5-ESPOS, Linux Enterprise High Performance Computing 15 SP5-LTSSkernel-64kb, kernel-docs, kernel-syms and 3 more5.14.21-150500.55.182.1SUSE-SU-2026:3595-1
SUSELinux Enterprise High Performance Computing 15 SP5-ESPOS, Linux Enterprise High Performance Computing 15 SP5-LTSS, Linux Enterprise Micro 5.5 and 2 morekernel-default-base5.14.21-150500.55.182.1.150500.6.85.2SUSE-SU-2026:3595-1
SUSELinux Enterprise Live Patching 12 SP5kernel-default4.12.14-122.323.1SUSE-SU-2026:3594-1
SUSELinux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_861-8.3.1SUSE-SU-2026:3594-1
SUSELinux Enterprise Live Patching 15 SP5kernel-default5.14.21-150500.55.182.1SUSE-SU-2026:3595-1
SUSELinux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5_Update_441-150500.11.5.1SUSE-SU-2026:3595-1
SUSELinux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7-RT_Update_181-150700.1.5.1SUSE-SU-2026:3130-1
SUSELinux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7_Update_191-150700.15.3.4SUSE-SU-2026:3166-1
SUSELinux Enterprise Micro 5.5kernel-rt, kernel-source-rt5.14.21-150500.13.156.1SUSE-SU-2026:3617-1
SUSELinux Enterprise Micro 5.5kernel-source, kernel-default5.14.21-150500.55.182.1SUSE-SU-2026:3595-1
19 more for SUSE in the JSON and on SUSE's page.
openSUSELeap 16.0kernel-default-base6.12.0-160000.37.1.160000.2.19openSUSE-SU-2026:21555-1
openSUSELeap 16.0kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160000.37.1openSUSE-SU-2026:21555-1
Alpaquita23linux-lts6.1.167-r0BELL-CVE-2026-43211
Alpaquita25linux-lts6.12.80-r0BELL-CVE-2026-43211
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2026-43211

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Low.

Red Hat's statement

This flaw is rated as having a Low impact because triggering the lock imbalance requires specific concurrent PCI slot or bus management operations that are typically restricted to privileged local users or specific hardware management events. While an erroneous unlock could release another thread's lock and lead to kernel warnings or denial of service, it cannot be leveraged to compromise confidentiality or integrity. Furthermore, typical workloads without active PCI slot manipulation or hotplug operations will rarely traverse this specific failure code path.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelOut of support scope
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelOut of support scope
Red Hat Enterprise Linux 9kernel-rtFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-43211.

Attack patterns (CAPEC)

  • CAPEC-25 Forced Deadlock Likelihood: Low · Severity: High
  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-27 Leveraging Race Conditions via Symbolic Links Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON