media: amd: isp4: fix self-deadlock in isp4sd_pwron_and_init() error path
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
media: amd: isp4: fix self-deadlock in isp4sd_pwron_and_init() error path
isp4sd_pwron_and_init() holds ops_mutex via guard(mutex) and, on any init failure, jumps to err_deinit and calls isp4sd_pwroff_and_deinit(). That helper takes the same ops_mutex, re-acquiring a non-recursive mutex already held by the current thread, so any init failure deadlocks.
Unwind the error path in stages instead, releasing only what each failure point acquired. This also avoids the issues that an unconditional teardown would hit at the earlier failures, such as a runtime-PM underflow from pm_runtime_resume_and_get() and MMIO access while the device is unpowered.
From the CVE record · Linux
The Linux kernel's AMD ISP4 driver can deadlock when initialization fails: its error path tries to acquire a mutex already held by the same thread. The input does not specify whether an attacker can trigger the failure or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with the AMD ISP4 driver should check their versions; affected versions are not specified.