CVE Catalog

CVE-2026-90238

Unknown
Published: Translated: NVD NIST

Summary

In the Linux kernel's media: amd: isp4 driver, the function isp4sd_pwron_and_init() causes a deadlock in the error path by re-acquiring the ops_mutex it already holds. The fix changes error handling to release resources in stages, avoiding the deadlock and other issues like runtime-PM underflow.

Risk Assessment

The deadlock can hang the system or driver, leading to unresponsiveness and requiring a reboot. It may also cause device power management issues.

Recommendation

Apply the Linux kernel patch that changes the error path in isp4sd_pwron_and_init() to release resources in stages, avoiding re-acquiring the mutex.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS