Bug 2536677 (CVE-2026-90238) - CVE-2026-90238 kernel: media: amd: isp4: fix self-deadlock in isp4sd_pwron_and_init() error path
Summary: CVE-2026-90238 kernel: media: amd: isp4: fix self-deadlock in isp4sd_pwron_an...
Keywords:
Status: NEW
Alias: CVE-2026-90238
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-17 19:04 UTC by OSIDB Bzimport
Modified: 2026-10-13 13:26 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-17 19:04:20 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.