Linux PCI: Fix missing bridge lock in pci_bus_lock() preventing race condition

From this webpage screenshot, we can extract the following key information about the vulnerability: 1. Vulnerability Description: - Title: PCI: Add missing bridge lock to pci_bus_lock() - Description: This vulnerability arises from the absence of locking for bridge devices in the function, which may lead to an unlocked secondary bus reset when a bridge device is reset. 2. Triggering Conditions: - Triggering Condition: In the function, several calls start from and use to lock everything before issuing a reset, but they exclude the bridge device itself. 3. Mitigation Measures: - Mitigation: To fix this issue, it is recommended to add for the device within the function, in both "bus" and "cxl_bus" reset scenarios, before calling . 4. Code Changes: - Code Changes: The code now includes locking for bridge devices, as shown below: 5. Reporting and Discussion: - Reporter: Imre Deak - Discussion Link: https://lore.kernel.org/r/171711747501.1628941.15217746952476635316.stgit@dwillia2-xfh.jf.intel.com - Closure Link: http://lore.kernel.org/r/6657833b3b5ae_14984b29437@dwillia2-xfh.jf.intel.com.notmuch 6. Sign-offs and Testing: - Sign-offs: Dan Williams, Keith Busch, Bjorn Helgaas, Hans de Goede, Kalle Valo, Dave Jiang - Testing: Hans de Goede, Kalle Valo, Dave Jiang This information helps us understand the vulnerability's context, triggering conditions, mitigation steps, and related discussions and testing activities.

Goal Reached Thanks to every supporter — we hit 100%!

Linux PCI: Fix missing bridge lock in pci_bus_lock() preventing race condition