Not a U.S. government website. NDD is an independent vulnerability database by Volerion and is not affiliated with or endorsed by NIST or NVD.
VOLERION
Volerion Security Research

NOT DEFERRED DATABASE

VULNERABILITIES

CVE-2025-21951 Details

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.

Metrics

CVSS 3.x Severity and Vector Strings:

References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.

Weakness Enumeration

CWE-IDCWE NameSource
CWE-667Improper Locking[email protected]
CWE-667Improper LockingCISA-ADP

Affected Products

ProductVersions
linux linux kernel
>= 5.12, < 5.15.179
>= 5.16, < 6.1.131
>= 6.2, < 6.6.83
>= 6.7, < 6.12.19
>= 6.13, < 6.13.7

CPE

  • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.14:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.14:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.14:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.14:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.14:rc5:*:*:*:*:*:*

Remediation

  • No remediation found in references.

Change History

6 change records found show changes


QUICK INFO

CVE Dictionary Entry:
CVE-2025-21951
NVD Published Date:
Apr 1, 2025
NVD Last Modified:
Jun 17, 2026
Source:
kernel.org
CVE-2025-21951 Details - Not Deferred