CVE-2025-21951: bus: mhi: host: pci_generic: Use pci_try_reset_function() to avoid deadlock
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1f9eb7078bc6b5fb5cbfbcb37c4bc01685332b95, 62505657475c245c9cd46e42ac01026d1e61f027, 7746f3bb8917fccb4571a576f3837d80fc513054; azl3 kernel 6.6.82.1-1 on Azure Linux 3.0 6.6.85.1-2; azl3 kernel 6.6.85.1-2 on Azure Linux 3.0 6.6.85.1-2.
Low priority for now. Upgrade to Linux Linux 1f9eb7078bc6b5fb5cbfbcb37c4bc01685332b95, 62505657475c245c9cd46e42ac01026d1e61f027, 7746f3bb8917fccb4571a576f3837d80fc513054; azl3 kernel 6.6.82.1-1 on Azure Linux 3.0 6.6.85.1-2; azl3 kernel 6.6.85.1-2 on Azure Linux 3.0 6.6.85.1-2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: bus: mhi: host: pci_generic: Use pci_try_reset_function() to avoid deadlock There are multiple places from where the recovery work gets scheduled asynchronously. Also, there are multiple places where the caller waits synchronously for the recovery to be completed. One such place is during the PM shutdown() callback. If the device is not alive during recovery_work, it will try to reset the device using pci_reset_function(). This function internally will take the device_lock() first before resetting the device. By this time, if the lock has already been acquired, then recovery_work will get stalled while waiting for the lock. And if the lock was already acquired by the caller which waits for the recovery_work to be completed, it will lead to deadlock. This is what happened on the X1E80100 CRD device when the device died before shutdown() callback. Driver core calls the driver's shutdown() callback while holding the device_lock() leading to deadlock. And this deadlock scenario can occur on other paths as well, like during the PM suspend() callback, where the driver core would hold the device_lock() before calling driver's suspend() callback. And if the recovery_work was already started, it could lead to deadlock. This is also observed on the X1E80100 CRD. So to fix both issues, use pci_try_reset_function() in recovery_work. This function first checks for the availability of the device_lock() before trying to reset the device. If the lock is available, it will acquire it and reset the device. Otherwise, it will return -EAGAIN. If that happens, recovery_work will fail with the error message "Recovery failed" as not much could be done.
- Published
- Apr 1, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- CWE-667
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.12affected
- 7389337f0a78ea099c47f0af08f64f20c52ab4ba and later · before 7746f3bb8917fccb4571a576f3837d80fc513054affected · git
- 7389337f0a78ea099c47f0af08f64f20c52ab4ba and later · before 7a5ffadd54fe2662f5c99cdccf30144d060376f7affected · git
- 7389337f0a78ea099c47f0af08f64f20c52ab4ba and later · before 1f9eb7078bc6b5fb5cbfbcb37c4bc01685332b95affected · git
- 7389337f0a78ea099c47f0af08f64f20c52ab4ba and later · before 985d3cf56d8745ca637deee273929e01df449f85affected · git
- 7389337f0a78ea099c47f0af08f64f20c52ab4ba and later · before 62505657475c245c9cd46e42ac01026d1e61f027affected · git
- 7389337f0a78ea099c47f0af08f64f20c52ab4ba and later · before a321d163de3d8aa38a6449ab2becf4b1581aed96affected · git
- before 5.12not affected · semver
- 5.15.179 and later · up to and including 5.15.*not affected · semver
- 6.1.131 and later · up to and including 6.1.*not affected · semver
Affected versions · NVD (6)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.12 and later · before 5.15.179
- linux linux kernel5.16 and later · before 6.1.131
- linux linux kernel6.2 and later · before 6.6.83
- linux linux kernel6.7 and later · before 6.12.19
- linux linux kernel6.13 and later · before 6.13.7
- linux linux kernel6.14
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.133-1 | 6.1.133-1 |
| Debian:13 | linux | before 6.12.19-1 | 6.12.19-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-21949Apr 1, 2025 · LoongArch: Set hugetlb mmap base address aligned with pmd size22Monitor
- ← EarlierCVE-2025-21950Apr 1, 2025 · drivers: virt: acrn: hsm: Use kzalloc to avoid info leak in pmcmd_ioctl28Monitor
- Later →CVE-2025-21952Apr 1, 2025 · HID: corsair-void: Update power supply values with a unified work handler22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1f9eb7078bc6b5fb5cbfbcb37c4bc01685332b95 | Vendor (CNA) |
| Linux Linux | 62505657475c245c9cd46e42ac01026d1e61f027 | Vendor (CNA) |
| Linux Linux | 7746f3bb8917fccb4571a576f3837d80fc513054 | Vendor (CNA) |
| Linux Linux | 7a5ffadd54fe2662f5c99cdccf30144d060376f7 | Vendor (CNA) |
| Linux Linux | 985d3cf56d8745ca637deee273929e01df449f85 | Vendor (CNA) |
| Linux Linux | a321d163de3d8aa38a6449ab2becf4b1581aed96 | Vendor (CNA) |
| azl3 kernel 6.6.82.1-1 on Azure Linux 3.0 | 6.6.85.1-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.85.1-2 on Azure Linux 3.0 | 6.6.85.1-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.176.3-3 on CBL Mariner 2.0 | 5.15.180.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.176.3-3 on CBL-Mariner 2.0 | 5.15.180.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.180.1-1 on CBL Mariner 2.0 | 5.15.180.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.133-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-667 · Improper LockingCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/62505657475c245c9cd46e42ac01026d1e61f027
- git.kernel.org/stable/c/7746f3bb8917fccb4571a576f3837d80fc513054
- git.kernel.org/stable/c/7a5ffadd54fe2662f5c99cdccf30144d060376f7
- git.kernel.org/stable/c/985d3cf56d8745ca637deee273929e01df449f85
- git.kernel.org/stable/c/a321d163de3d8aa38a6449ab2becf4b1581aed96
- lists.debian.org/debian-lts-announce/2025/05/msg00045.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.