CVE-2026-72290 Linux CVE debrief

Who should care

Administrators and users of Linux systems utilizing KVM for s390 should be aware of this vulnerability and take steps to apply patches or mitigations. They should review Linux kernel and KVM for s390 configurations for potential vulnerabilities and monitor system logs for signs of the issue. Security teams should prioritize patching and verify system integrity.

Technical summary

The Linux kernel's KVM for s390 has a vulnerability where a GISC refcount leak occurs on AIF enable failure. This happens because kvm_s390_gisc_register() registers the guest ISC before completing setup steps, and if any step fails, it unwinds local state but does not unregister the GISC reference. The issue arises from improper handling of GISC references during setup failures, potentially leading to resource leaks.

Defensive priority

Apply patches to address the GISC refcount leak in KVM for s390; monitor system logs for signs of the issue.

Recommended defensive actions

• Apply patches to address the GISC refcount leak in KVM for s390
• Monitor system logs for signs of the issue
• Review Linux kernel and KVM for s390 configurations for potential vulnerabilities
• 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
• 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

Evidence notes

The CVE record and NVD entry provide limited information about the vulnerability. Further analysis of Linux kernel sources and KVM for s390 may be necessary to fully understand the issue. The vulnerability arises from kvm_s390_gisc_register() registering the guest ISC before completing setup steps, and if any step fails, it unwinds local state but does not unregister the GISC reference. Evidence is limited, and defenders should verify patch application and system logs for signs of the issue.

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.