CVE-2024-46750: Vulnerability in Linux Linux
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]
AI Analysis
Technical Summary
CVE-2024-46750 is a vulnerability identified in the Linux kernel's PCI subsystem, specifically related to the locking mechanisms used during PCI bus resets. The issue arises from missing locking of the PCI bridge device during the pci_bus_lock() operation. The vulnerability was discovered through lock dependency (lockdep) analysis, which revealed that the pci_bridge_secondary_bus_reset function triggers secondary bus resets without properly locking the bridge device. While pci_bus_reset() uses pci_bus_lock() to lock the bus before reset, this lock does not cover the bridge device itself, leading to potential race conditions or deadlocks. The fix involves adding pci_dev_lock() calls for the bridge device (bus->self) to the pci_bus_lock() procedure, ensuring that the bridge is properly locked during reset operations. This change prevents recursive locking deadlocks and improves the stability and correctness of PCI bus reset sequences. The vulnerability affects Linux kernel versions identified by the commit hash 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and was published on September 18, 2024. No known exploits are reported in the wild at this time, and no CVSS score has been assigned yet. The vulnerability is technical and low-level, related to kernel synchronization primitives in PCI device management.
Potential Impact
For European organizations, this vulnerability primarily affects systems running vulnerable Linux kernel versions that manage PCI devices, including servers, workstations, and embedded systems. Potential impacts include system instability, kernel panics, or deadlocks during PCI bus reset operations, which could lead to temporary denial of service or degraded system performance. In environments with high PCI device usage, such as data centers, telecommunications infrastructure, or industrial control systems, this could disrupt critical operations. Although there is no evidence of remote code execution or privilege escalation directly linked to this vulnerability, the risk of system crashes or hangs could impact availability and operational continuity. Organizations relying on Linux-based infrastructure for critical services should be aware of this issue, especially if they use hardware configurations with complex PCI topologies or virtualized environments where PCI device resets are frequent. The absence of known exploits reduces immediate risk, but unpatched systems remain vulnerable to potential future exploitation or stability issues.
Mitigation Recommendations
European organizations should prioritize updating their Linux kernels to versions that include the patch for CVE-2024-46750 as soon as they become available from their Linux distribution vendors. Since the vulnerability relates to kernel-level locking, applying official kernel updates or backported patches is the most effective mitigation. System administrators should audit their PCI device configurations and monitor kernel logs for warnings related to pci_bridge_secondary_bus_reset or pci_reset_bus functions, which may indicate attempts to trigger the vulnerability or system instability. For critical systems, consider implementing kernel live patching solutions to minimize downtime during updates. Additionally, organizations should test kernel updates in staging environments to ensure compatibility with their hardware and workloads, particularly for systems with complex PCI device arrangements. Maintaining robust backup and recovery procedures will help mitigate potential availability impacts. Finally, monitoring vendor advisories and security bulletins for updates on this vulnerability and any emerging exploit reports is recommended.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain, Poland
CVE-2024-46750: Vulnerability in Linux Linux
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/20240711193650.701834-1-kbusch@meta.com]
AI-Powered Analysis
Technical Analysis
CVE-2024-46750 is a vulnerability identified in the Linux kernel's PCI subsystem, specifically related to the locking mechanisms used during PCI bus resets. The issue arises from missing locking of the PCI bridge device during the pci_bus_lock() operation. The vulnerability was discovered through lock dependency (lockdep) analysis, which revealed that the pci_bridge_secondary_bus_reset function triggers secondary bus resets without properly locking the bridge device. While pci_bus_reset() uses pci_bus_lock() to lock the bus before reset, this lock does not cover the bridge device itself, leading to potential race conditions or deadlocks. The fix involves adding pci_dev_lock() calls for the bridge device (bus->self) to the pci_bus_lock() procedure, ensuring that the bridge is properly locked during reset operations. This change prevents recursive locking deadlocks and improves the stability and correctness of PCI bus reset sequences. The vulnerability affects Linux kernel versions identified by the commit hash 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and was published on September 18, 2024. No known exploits are reported in the wild at this time, and no CVSS score has been assigned yet. The vulnerability is technical and low-level, related to kernel synchronization primitives in PCI device management.
Potential Impact
For European organizations, this vulnerability primarily affects systems running vulnerable Linux kernel versions that manage PCI devices, including servers, workstations, and embedded systems. Potential impacts include system instability, kernel panics, or deadlocks during PCI bus reset operations, which could lead to temporary denial of service or degraded system performance. In environments with high PCI device usage, such as data centers, telecommunications infrastructure, or industrial control systems, this could disrupt critical operations. Although there is no evidence of remote code execution or privilege escalation directly linked to this vulnerability, the risk of system crashes or hangs could impact availability and operational continuity. Organizations relying on Linux-based infrastructure for critical services should be aware of this issue, especially if they use hardware configurations with complex PCI topologies or virtualized environments where PCI device resets are frequent. The absence of known exploits reduces immediate risk, but unpatched systems remain vulnerable to potential future exploitation or stability issues.
Mitigation Recommendations
European organizations should prioritize updating their Linux kernels to versions that include the patch for CVE-2024-46750 as soon as they become available from their Linux distribution vendors. Since the vulnerability relates to kernel-level locking, applying official kernel updates or backported patches is the most effective mitigation. System administrators should audit their PCI device configurations and monitor kernel logs for warnings related to pci_bridge_secondary_bus_reset or pci_reset_bus functions, which may indicate attempts to trigger the vulnerability or system instability. For critical systems, consider implementing kernel live patching solutions to minimize downtime during updates. Additionally, organizations should test kernel updates in staging environments to ensure compatibility with their hardware and workloads, particularly for systems with complex PCI device arrangements. Maintaining robust backup and recovery procedures will help mitigate potential availability impacts. Finally, monitoring vendor advisories and security bulletins for updates on this vulnerability and any emerging exploit reports is recommended.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-09-11T15:12:18.267Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9826c4522896dcbe11af
Added to database: 5/21/2025, 9:08:54 AM
Last enriched: 6/29/2025, 1:11:57 AM
Last updated: 8/3/2025, 6:28:22 AM
Views: 13
Related Threats
CVE-2025-9050: SQL Injection in projectworlds Travel Management System
MediumCVE-2025-9047: SQL Injection in projectworlds Visitor Management System
MediumCVE-2025-9046: Stack-based Buffer Overflow in Tenda AC20
HighCVE-2025-9028: SQL Injection in code-projects Online Medicine Guide
MediumCVE-2025-26709: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in ZTE F50
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.