PCI: Fix pci_slot_trylock() error handling
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.252, 5.15.202, 6.1.165, 6.6.128, 4.20, and 5 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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]
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From e2355d513b89a2cb511b4ded0deb426cdb01acd0 · fixed in ebb27b7399ab8b9eb1f792b329aa5f6250c590d4; From 04e85a3285b0e5c5af6fd2c0fd6e95ffecc01945 · fixed in fbe06a3058114bf95a17a4941b205f4b321c6f0a; From 7253b4fed46471cc247c6cacefac890a8472c083 · fixed in 943ed56606a7ab2fe5a99cad572dd17d484310c7; From 78c6e39fef5c428960aff742149bba302dd46f5a · fixed in a19b61fdb958ffadbba85b43c991eb9fc70c1c1c; From a4e772898f8bf2e7e1cf661a12c60a5612c4afab · fixed in 0425aaf20b407d2f2cf3bf469808e4a35f9abb8b; From a4e772898f8bf2e7e1cf661a12c60a5612c4afab · fixed in bd435f4b738130d732ef64e0e57e45185f77165d; From a4e772898f8bf2e7e1cf661a12c60a5612c4afab · fixed in 8b08ea9690b212b7bf7f12414039259cf34b1aa0; From a4e772898f8bf2e7e1cf661a12c60a5612c4afab · fixed in 9368d1ee62829b08aa31836b3ca003803caf0b72; From 5.10.226 · fixed in 5.10.252; From 5.15.167 · fixed in 5.15.202; From 6.1.110 · fixed in 6.1.165; From 6.6.51 · fixed in 6.6.128; From 4.19.322 · fixed in 4.20; From 5.4.284 · fixed in 5.5; From 6.10.10 · fixed in 6.11
- Linux Linux
6.11
- KernelLinux
fixed in 5.10.252; From 5.11.0 · fixed in 5.15.202; From 5.16.0 · fixed in 6.1.165; From 6.2.0 · fixed in 6.6.128; From 6.7.0 · fixed in 6.12.75; From 6.11.0 · fixed in 6.18.16; From 6.13.0 · fixed in 6.19.6
References 8
git.kernel.org
- stable/c/ebb27b7399ab8b9eb1f792b329aa5f6250c590d4
- stable/c/fbe06a3058114bf95a17a4941b205f4b321c6f0a
- stable/c/943ed56606a7ab2fe5a99cad572dd17d484310c7
- stable/c/a19b61fdb958ffadbba85b43c991eb9fc70c1c1c
- stable/c/0425aaf20b407d2f2cf3bf469808e4a35f9abb8b
- stable/c/bd435f4b738130d732ef64e0e57e45185f77165d
- stable/c/8b08ea9690b212b7bf7f12414039259cf34b1aa0
- stable/c/9368d1ee62829b08aa31836b3ca003803caf0b72