Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-21951bus: mhi: host: pci_generic: Use pci_try_reset_function() to avoid deadlock

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 14 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-21951, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 7389337f0a78ea099c47f0af08f64f20c52ab4ba – < 7746f3bb8917fccb4571a576f3837d80fc513054
    • affected 7389337f0a78ea099c47f0af08f64f20c52ab4ba – < 7a5ffadd54fe2662f5c99cdccf30144d060376f7
    • affected 7389337f0a78ea099c47f0af08f64f20c52ab4ba – < 1f9eb7078bc6b5fb5cbfbcb37c4bc01685332b95
    • affected 7389337f0a78ea099c47f0af08f64f20c52ab4ba – < 985d3cf56d8745ca637deee273929e01df449f85
    • affected 7389337f0a78ea099c47f0af08f64f20c52ab4ba – < 62505657475c245c9cd46e42ac01026d1e61f027
    • affected 7389337f0a78ea099c47f0af08f64f20c52ab4ba – < a321d163de3d8aa38a6449ab2becf4b1581aed96
  • Linux · Linux

    • affected 5.12
    • unaffected < 5.12
    • unaffected 5.15.179 – ≤ 5.15.*
    • unaffected 6.1.131 – ≤ 6.1.*
    • unaffected 6.6.83 – ≤ 6.6.*
    • unaffected 6.12.19 – ≤ 6.12.*
    • unaffected 6.13.7 – ≤ 6.13.*
    • unaffected 6.14 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-21951 badge
[![CVE-2025-21951](https://cveledger.app/badge/CVE-2025-21951.svg)](https://cveledger.app/cve/CVE-2025-21951)

Record last updated .