System hang via contended device lock
Published Apr 1, 2025 · Updated May 11, 2026
Improper locking in the MHI PCI host driver in Linux allows local users to encounter a system hang during shutdown or suspend. The recovery_work handler calls pci_reset_function(), which waits for device_lock even when the power-management caller holds that lock and synchronously waits for recovery to finish. The deadlock requires an MHI PCI device to become unresponsive; Ubuntu reports that attackers cannot reliably invoke or influence that hardware condition, limiting the consequence to an availability interruption.
Summary
What happened
Improper locking in the MHI PCI host driver in Linux allows local users to encounter a system hang during shutdown or suspend. The recovery_work handler calls pci_reset_function(), which waits for device_lock even when the power-management caller holds that lock and synchronously waits for recovery to finish. The deadlock requires an MHI PCI device to become unresponsive; Ubuntu reports that attackers cannot reliably invoke or influence that hardware condition, limiting the consequence to an availability interruption.
The record
- CVE
- CVE-2025-21951
- Published
- Apr 1, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 1, 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=5.12
- Affected versionversion=7389337f0a78ea099c47f0af08f64f20c52ab4ba <1f9eb7078bc6b5fb5cbfbcb37c4bc01685332b95
- Affected versionversion=7389337f0a78ea099c47f0af08f64f20c52ab4ba <62505657475c245c9cd46e42ac01026d1e61f027
- Affected versionversion=7389337f0a78ea099c47f0af08f64f20c52ab4ba <7746f3bb8917fccb4571a576f3837d80fc513054
- Affected versionversion=7389337f0a78ea099c47f0af08f64f20c52ab4ba <7a5ffadd54fe2662f5c99cdccf30144d060376f7
- Affected versionversion=7389337f0a78ea099c47f0af08f64f20c52ab4ba <985d3cf56d8745ca637deee273929e01df449f85
- Affected versionversion=7389337f0a78ea099c47f0af08f64f20c52ab4ba <a321d163de3d8aa38a6449ab2becf4b1581aed96
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