System hang via PCI lock-order inversion
Published Feb 26, 2025 · Updated May 11, 2026
Improper locking in Linux kernel PCI code allows local users to hang affected systems by racing SR-IOV configuration with a PCI reset. The pci_dev_lock() path takes the configuration-space access lock before the device lock, while sriov_numvfs_store() takes the same locks in reverse order. The flaw requires local low-privileged access and concurrent SR-IOV reconfiguration and PCI device reset operations; a successful race deadlocks the kernel and interrupts the system.
Summary
What happened
Improper locking in Linux kernel PCI code allows local users to hang affected systems by racing SR-IOV configuration with a PCI reset. The pci_dev_lock() path takes the configuration-space access lock before the device lock, while sriov_numvfs_store() takes the same locks in reverse order. The flaw requires local low-privileged access and concurrent SR-IOV reconfiguration and PCI device reset operations; a successful race deadlocks the kernel and interrupts the system.
The record
- CVE
- CVE-2022-49434
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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=17530e71e0166a37f8e20a9b7bcf1d50ae3cff8e <2cdd5284035322795b0964f899eefba254cfe483
- Affected versionversion=17530e71e0166a37f8e20a9b7bcf1d50ae3cff8e <59ea6b3ae51df7cd6bfd84c9c0030609b9315622
- Affected versionversion=17530e71e0166a37f8e20a9b7bcf1d50ae3cff8e <a91ee0e9fca9d7501286cfbced9b30a33e52740a
- Affected versionversion=17530e71e0166a37f8e20a9b7bcf1d50ae3cff8e <aed6d4d519210c28817948f34c53b6e058e0456c
- Affected versionversion=17530e71e0166a37f8e20a9b7bcf1d50ae3cff8e <c3c6dc1853b8bf3c718f96fd8480a6eb09ba4831
- Affected versionversion=17530e71e0166a37f8e20a9b7bcf1d50ae3cff8e <c9a81f9ed6ae3554621d6a50220b1bc74b67d81e
- Affected versionversion=17530e71e0166a37f8e20a9b7bcf1d50ae3cff8e <ea047f51172aa68841adef7f52d375002438b8f0
- Affected versionversion=17530e71e0166a37f8e20a9b7bcf1d50ae3cff8e <eff3587b9c01439b738298475e555c028ac9f55e
- Affected versionversion=4.13
What conditions does exploitation require?
What is affected?
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.
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