CVE-2024-46750
GNU/Linux PCI Multiple Lock Bug
Description
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/[email protected]]
INFO
Published Date :
Sept. 18, 2024, 8:15 a.m.
Last Modified :
Sept. 30, 2024, 1:27 p.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
3.6
Exploitability Score :
1.8
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-46750.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-46750 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-46750 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Sep. 30, 2024
Action Type Old Value New Value Added CVSS V3.1 NIST AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Changed Reference Type https://git.kernel.org/stable/c/04e85a3285b0e5c5af6fd2c0fd6e95ffecc01945 No Types Assigned https://git.kernel.org/stable/c/04e85a3285b0e5c5af6fd2c0fd6e95ffecc01945 Patch Changed Reference Type https://git.kernel.org/stable/c/0790b89c7e911003b8c50ae50e3ac7645de1fae9 No Types Assigned https://git.kernel.org/stable/c/0790b89c7e911003b8c50ae50e3ac7645de1fae9 Patch Changed Reference Type https://git.kernel.org/stable/c/7253b4fed46471cc247c6cacefac890a8472c083 No Types Assigned https://git.kernel.org/stable/c/7253b4fed46471cc247c6cacefac890a8472c083 Patch Changed Reference Type https://git.kernel.org/stable/c/78c6e39fef5c428960aff742149bba302dd46f5a No Types Assigned https://git.kernel.org/stable/c/78c6e39fef5c428960aff742149bba302dd46f5a Patch Changed Reference Type https://git.kernel.org/stable/c/81c68e218ab883dfa368460a59b674084c0240da No Types Assigned https://git.kernel.org/stable/c/81c68e218ab883dfa368460a59b674084c0240da Patch Changed Reference Type https://git.kernel.org/stable/c/a4e772898f8bf2e7e1cf661a12c60a5612c4afab No Types Assigned https://git.kernel.org/stable/c/a4e772898f8bf2e7e1cf661a12c60a5612c4afab Patch Changed Reference Type https://git.kernel.org/stable/c/df77a678c33871a6e4ac5b54a71662f1d702335b No Types Assigned https://git.kernel.org/stable/c/df77a678c33871a6e4ac5b54a71662f1d702335b Patch Changed Reference Type https://git.kernel.org/stable/c/e2355d513b89a2cb511b4ded0deb426cdb01acd0 No Types Assigned https://git.kernel.org/stable/c/e2355d513b89a2cb511b4ded0deb426cdb01acd0 Patch Added CWE NIST CWE-667 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions up to (excluding) 4.19.322 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.20 up to (excluding) 5.4.284 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.5 up to (excluding) 5.10.226 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.167 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.110 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.51 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.10.10 -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Sep. 18, 2024
Action Type Old Value New Value Added Description 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/[email protected]] Added Reference kernel.org https://git.kernel.org/stable/c/0790b89c7e911003b8c50ae50e3ac7645de1fae9 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/df77a678c33871a6e4ac5b54a71662f1d702335b [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/e2355d513b89a2cb511b4ded0deb426cdb01acd0 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/04e85a3285b0e5c5af6fd2c0fd6e95ffecc01945 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/7253b4fed46471cc247c6cacefac890a8472c083 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/78c6e39fef5c428960aff742149bba302dd46f5a [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/81c68e218ab883dfa368460a59b674084c0240da [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/a4e772898f8bf2e7e1cf661a12c60a5612c4afab [No types assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-46750 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-46750
weaknesses.