Vulnerability · Published Apr 1, 2025 · Assigned by Linux
CVE-2025-21951bus: mhi: host: pci_generic: Use pci_try_reset_function() to avoid deadlock
Medium 5.5
In plain English
A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 6% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official 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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.133-1 | DEBIAN-CVE-2025-21951 |
| Debian:13 | linux | 6.12.19-1 | DEBIAN-CVE-2025-21951 |
| Debian:14 | linux | 6.12.19-1 | DEBIAN-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux | 5.15.0-140.150 | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux | 6.8.0-84.84 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1084.91 | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1039.41 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1039.41~22.04.1 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1089.98 | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1038.44 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | 6.11.0-1018.18~24.04.1 | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | 6.11.0-1018.18~24.04.1 | USN-7628-1 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1036.42~22.04.1 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1089.98.1 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | 6.8.0-1025.27 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1083.92 | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1040.42 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | 6.11.0-1016.16~24.04.1 | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | 6.11.0-1016.16~24.04.1 | USN-7605-1 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1040.42~22.04.1 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1081.87 | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1036.40 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1066.74 | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1023.25 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | 6.11.0-28.28~24.04.1 | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | 6.11.0-28.28~24.04.1 | USN-7605-1 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-85.85~22.04.1 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1076.79 | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1037.37 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1037.37~22.04.1 | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-intel | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1079.85 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1080.85 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-140.150 | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-84.84.1 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | 6.11.0-1015.16~24.04.2 | USN-7605-2 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | 6.11.0-1015.16~24.04.2 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-84.84.1~22.04.1 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1078.79 | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1039.42 | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | 6.11.0-1012.12 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1039.42~22.04.1 | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1039.42.1 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1037.37 | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1010.10 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1026.26 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | 6.11.0-1024.24 | USN-7606-1 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | 6.11.0-1024.24 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1081.87 | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1037.38 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1037.38~22.04.1 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1078.81 | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1039.43 | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-84.84~22.04.1 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2025-21951 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1018.19 | UBUNTU-CVE-2025-21951 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1050.54 | UBUNTU-CVE-2025-21951 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 7389337f0a78ea099c47f0af08f64f20c52ab4ba – before 7746f3bb8917fccb4571a576f3837d80fc5130547389337f0a78ea099c47f0af08f64f20c52ab4ba – before 7a5ffadd54fe2662f5c99cdccf30144d060376f77389337f0a78ea099c47f0af08f64f20c52ab4ba – before 1f9eb7078bc6b5fb5cbfbcb37c4bc01685332b957389337f0a78ea099c47f0af08f64f20c52ab4ba – before 985d3cf56d8745ca637deee273929e01df449f857389337f0a78ea099c47f0af08f64f20c52ab4ba – before 62505657475c245c9cd46e42ac01026d1e61f0277389337f0a78ea099c47f0af08f64f20c52ab4ba – before a321d163de3d8aa38a6449ab2becf4b1581aed96 |
| Linux | Linux | 5.12 |
Weakness: CWE-667 · Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
References
- https://git.kernel.org/stable/c/7746f3bb8917fccb4571a576f3837d80fc513054
- https://git.kernel.org/stable/c/7a5ffadd54fe2662f5c99cdccf30144d060376f7
- https://git.kernel.org/stable/c/1f9eb7078bc6b5fb5cbfbcb37c4bc01685332b95
- https://git.kernel.org/stable/c/985d3cf56d8745ca637deee273929e01df449f85
- https://git.kernel.org/stable/c/62505657475c245c9cd46e42ac01026d1e61f027
- https://git.kernel.org/stable/c/a321d163de3d8aa38a6449ab2becf4b1581aed96
- https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html