CVE-2026-90239 Linux CVE debrief

Who should care

Linux kernel maintainers, users, administrators, and security teams should assess exposure and prioritize verification of affected systems, considering potential denial-of-service (DoS) attacks and elevation of privileges. They should review and apply patches, verify affected versions, and monitor system logs for potential memory leak issues.

Why it matters

A memory leak vulnerability was found in the Linux kernel's media: amd: isp4: release partial allocations in isp4if_alloc_fw_gpumem(). The vulnerability can cause system resource exhaustion, potential denial-of-service (DoS) attacks, and elevation of privileges may be possible. Linux kernel maintainers and users should assess exposure and prioritize verification of affected systems.

• Memory leak vulnerability can cause system resource exhaustion
• Potential denial-of-service (DoS) attacks
• Elevation of privileges may be possible

Technical summary

The vulnerability is caused by a memory leak in the isp4if_alloc_fw_gpumem() function, which allocates several GPU memory pools in sequence. If one of them fails, it jumps to error_no_memory and returns -ENOMEM without releasing the pools that were already allocated, leaking them. The already-allocated pools should be released before returning. This vulnerability can cause system resource exhaustion, potential denial-of-service (DoS) attacks, and elevation of privileges may be possible. Linux kernel maintainers and users should assess exposure and prioritize verification of affected systems.

Defensive priority

Linux kernel maintainers and users should assess exposure and prioritize verification of affected systems.

Recommended defensive actions

• Review and apply the patch to fix the memory leak vulnerability
• Verify affected Linux kernel versions and assess exposure
• Monitor system logs for potential memory leak issues
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record and source item provide details about the vulnerability, including its description and affected versions. The vulnerability is caused by a memory leak in the isp4if_alloc_fw_gpumem() function, which allocates several GPU memory pools in sequence. If one of them fails, it jumps to error_no_memory and returns -ENOMEM without releasing the pools that were already allocated, leaking them. The already-allocated pools should be released before returning. Linux kernel maintainers and users should assess exposure and prioritize

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.