AZL-59916

In the Linux kernel, the following vulnerability has been resolved:

bus: mhi: host: pcigeneric: Use pcitryresetfunction() 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 recoverywork, it will try to reset the device using pciresetfunction(). This function internally will take the devicelock() first before resetting the device. By this time, if the lock has already been acquired, then recoverywork will get stalled while waiting for the lock. And if the lock was already acquired by the caller which waits for the recoverywork 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 devicelock() before calling driver's suspend() callback. And if the recoverywork was already started, it could lead to deadlock. This is also observed on the X1E80100 CRD.

So to fix both issues, use pcitryresetfunction() in recoverywork. This function first checks for the availability of the devicelock() 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, recoverywork will fail with the error message "Recovery failed" as not much could be done.