System crash via unlocked PCI bridge reset
Published Sep 18, 2024 · Updated Aug 5, 2026
Improper PCI bridge locking in Linux 3.12 and later allows local users to crash the system by triggering a secondary bus reset. The pci_bus_lock function locks devices beneath a PCI bus but omits the bridge at bus->self, allowing pci_reset_bus callers to reset the bridge without its device lock. Low-privilege local access and a reachable PCI reset path are required; confidentiality and integrity are not affected.
Summary
What happened
Improper PCI bridge locking in Linux 3.12 and later allows local users to crash the system by triggering a secondary bus reset. The pci_bus_lock function locks devices beneath a PCI bus but omits the bridge at bus->self, allowing pci_reset_bus callers to reset the bridge without its device lock. Low-privilege local access and a reachable PCI reset path are required; confidentiality and integrity are not affected.
The record
- CVE
- CVE-2024-46750
- Published
- Sep 18, 2024
- Updated
- Aug 5, 2026
- Vendor
- Siemens
- Product
- SIPLUS S7-1500 CPU 1518-4 PN/DP MFP
- Classifications
- CWE-667, CWE-413, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 18, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=V3.1.0 <V3.1.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo