CVE-2026-90238 Linux CVE debrief

Who should care

Defenders responsible for Linux kernel systems using media: amd: isp4 should assess exposure and prioritize patching affected versions. This includes operators, platform administrators, vulnerability management teams, and security teams who need to review and update Linux kernel versions to ensure they are not using affected media: amd: isp4 code. Monitoring Linux kernel updates and patches is necessary to address potential impact on systems using media:  

Why it matters

A self-deadlock vulnerability in the Linux kernel's media: amd: isp4 module requires verification and patching of affected versions to prevent potential deadlocks.

• Verification of Linux kernel versions and patches is required to prevent potential deadlocks.
• Defenders should review and update Linux kernel versions to ensure they are not using affected media: amd: isp4 code.
• Monitoring Linux kernel updates and patches is necessary to address potential impact on systems using media: amd: isp4.

Technical summary

The vulnerability is caused by a self-deadlock in the isp4sd_pwron_and_init() error path of the Linux kernel's media: amd: isp4 module. When isp4sd_pwron_and_init() holds ops_mutex and encounters an init failure, it jumps to err_deinit and calls isp4sd_pwroff_and_deinit(), which re-acquires the same ops_mutex, causing a deadlock. This issue affects Linux kernel versions using media: amd: isp4 and requires verification and patching of affected versions to prevent potential deadlocks. Defenders should prioritize verifying and applying patches for Linux kernel versions affected by this vulnerability.

Defensive priority

Defenders should prioritize verifying and applying patches for Linux kernel versions affected by this vulnerability, particularly those using media: amd: isp4.

Recommended defensive actions

• Verify and apply patches for Linux kernel versions affected by this vulnerability
• Review and update Linux kernel versions to ensure they are not using affected media: amd: isp4 code
• Monitor Linux kernel updates and patches for potential impact on systems using media: amd: isp4
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description and affected versions. However, CVSS scores and severity are not provided. The vulnerability is caused by a self-deadlock in the isp4sd_pwron_and_init() error path of the Linux kernel's media: amd: isp4 module. The issue arises when isp4sd_pwron_and_init() holds ops_mutex and, on any init failure, jumps to err_deinit and calls isp4sd_pwroff_and_deinit(), which re-acquires the same ops_mutex, causing a deadlock. Defenders should verify Linux

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.