CVE-2026-90123 Linux CVE debrief

Who should care

Linux system administrators, security teams, and developers using irqchip/ast2700-intc should assess exposure and verify patch deployment to mitigate potential defensive consequences.

Why it matters

CVE-2026-90123 is a Linux kernel vulnerability in irqchip/ast2700-intc that requires patch deployment to prevent potential allocation issues with interrupts disabled. Linux system administrators, security teams, and developers should assess exposure and verify patch deployment.

• Verify patch deployment to prevent potential allocation issues with interrupts disabled
• Assess system configurations and inventory for irqchip/ast2700-intc usage
• Prioritize patching for version 7.2 and later

Technical summary

The Linux kernel vulnerability CVE-2026-90123 involves a resolved issue in irqchip/ast2700-intc to avoid allocating in the irq_domain activate() callback. The callback is called with interrupts disabled and a raw spinlock held. The allocation issue arises from fwnode_device_is_compatible() using GFP_KERNEL. This has been addressed by replacing fwnode_device_is_compatible() with of_device_is_compatible() for OF nodes.

Defensive priority

Assess exposure and verify patch deployment for Linux systems using irqchip/ast2700-intc, prioritizing version 7.2 and later.

Recommended defensive actions

• Assess Linux system exposure and verify patch deployment for irqchip/ast2700-intc
• Prioritize version 7.2 and later for patching
• Verify system configurations and inventory for irqchip/ast2700-intc usage
• 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 source item detail a Linux kernel vulnerability resolved to prevent allocation in the irq_domain activate() callback. The issue is caused by fwnode_device_is_compatible() allocating with GFP_KERNEL while interrupts are disabled and a raw spinlock is held.

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.