PCI: Add missing bridge lock to pci_bus_lock()
- 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 4.19.322, 5.4.284, 5.10.226, 5.15.167, 6.1.110, and 2 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: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: PCI: Add missing bridge lock to pci_bus_lock() One of the true positives that the cfg_access_lock lockdep effort identified is this sequence: WARNING: CPU: 14 PID: 1 at drivers/pci/pci.c:4886 pci_bridge_secondary_bus_reset+0x5d/0x70 RIP: 0010:pci_bridge_secondary_bus_reset+0x5d/0x70 Call Trace: <TASK> ? __warn+0x8c/0x190 ? pci_bridge_secondary_bus_reset+0x5d/0x70 ? report_bug+0x1f8/0x200 ? handle_bug+0x3c/0x70 ? exc_invalid_op+0x18/0x70 ? asm_exc_invalid_op+0x1a/0x20 ? pci_bridge_secondary_bus_reset+0x5d/0x70 pci_reset_bus+0x1d8/0x270 vmd_probe+0x778/0xa10 pci_device_probe+0x95/0x120 Where pci_reset_bus() users are triggering unlocked secondary bus resets. Ironically pci_bus_reset(), several calls down from pci_reset_bus(), uses pci_bus_lock() before issuing the reset which locks everything but the bridge itself. For the same motivation as adding: bridge = pci_upstream_bridge(dev); if (bridge) pci_dev_lock(bridge); to pci_reset_function() for the "bus" and "cxl_bus" reset cases, add pci_dev_lock() for @bus->self to pci_bus_lock(). [bhelgaas: squash in recursive locking deadlock fix from Keith Busch: https://lore.kernel.org/r/20240711193650.701834-1-kbusch@meta.com]
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 090a3c5322e900f468b3205b76d0837003ad57b2 · fixed in 0790b89c7e911003b8c50ae50e3ac7645de1fae9; From 090a3c5322e900f468b3205b76d0837003ad57b2 · fixed in df77a678c33871a6e4ac5b54a71662f1d702335b; From 090a3c5322e900f468b3205b76d0837003ad57b2 · fixed in e2355d513b89a2cb511b4ded0deb426cdb01acd0; From 090a3c5322e900f468b3205b76d0837003ad57b2 · fixed in 04e85a3285b0e5c5af6fd2c0fd6e95ffecc01945; From 090a3c5322e900f468b3205b76d0837003ad57b2 · fixed in 7253b4fed46471cc247c6cacefac890a8472c083; From 090a3c5322e900f468b3205b76d0837003ad57b2 · fixed in 78c6e39fef5c428960aff742149bba302dd46f5a; From 090a3c5322e900f468b3205b76d0837003ad57b2 · fixed in 81c68e218ab883dfa368460a59b674084c0240da; From 090a3c5322e900f468b3205b76d0837003ad57b2 · fixed in a4e772898f8bf2e7e1cf661a12c60a5612c4afab
- Linux Linux
3.12
- KernelLinux
From 3.12.0 · fixed in 4.19.322; From 4.20.0 · fixed in 5.4.284; From 5.5.0 · fixed in 5.10.226; From 5.11.0 · fixed in 5.15.167; From 5.16.0 · fixed in 6.1.110; From 6.2.0 · fixed in 6.6.51; From 6.7.0 · fixed in 6.10.10
References 8
git.kernel.org
- stable/c/0790b89c7e911003b8c50ae50e3ac7645de1fae9
- stable/c/df77a678c33871a6e4ac5b54a71662f1d702335b
- stable/c/e2355d513b89a2cb511b4ded0deb426cdb01acd0
- stable/c/04e85a3285b0e5c5af6fd2c0fd6e95ffecc01945
- stable/c/7253b4fed46471cc247c6cacefac890a8472c083
- stable/c/78c6e39fef5c428960aff742149bba302dd46f5a
- stable/c/81c68e218ab883dfa368460a59b674084c0240da
- stable/c/a4e772898f8bf2e7e1cf661a12c60a5612c4afab