CVE-2025-40161
Description
In the Linux kernel, the following vulnerability has been resolved:
mailbox: zynqmp-ipi: Fix SGI cleanup on unbind
The driver incorrectly determines SGI vs SPI interrupts by checking IRQ number < 16, which fails with dynamic IRQ allocation. During unbind, this causes improper SGI cleanup leading to kernel crash.
Add explicit irq_type field to pdata for reliable identification of SGI interrupts (type-2) and only clean up SGI resources when appropriate.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
In the Linux kernel, the zynqmp-ipi mailbox driver's SGI cleanup logic incorrectly determines interrupt type, causing a kernel crash on driver unbind.
Vulnerability
Details
In the Linux kernel's mailbox: zynqmp-ipi driver, the interrupt cleanup routine incorrectly identifies whether an interrupt is an SGI (Software Generated Interrupt) or SPI (Shared Peripheral Interrupt). The original code checks if the IRQ number is less than 16, but with dynamic IRQ allocation this comparison fails [1]. As a result, the driver treats SPI interrupts as SGIs during unbind, leading to improper cleanup of SGI resources and ultimately causing a kernel crash [1].
Exploitation and
Impact
The vulnerability is triggered during the driver unbind operation (e.g., module removal or device removal). No special privileges or network access are required; an unprivileged user or a system administrator performing a normal driver unbind can trigger the crash, resulting in a denial of service (system panic). The flaw lies in the driver's internal logic and does not require any specific attack sequence.
Mitigation
The fix introduces an explicit irq_type field to the driver's private data structure (pdata) to reliably distinguish SGI interrupts (type-2) from others. During cleanup, only SGI resources are released when the recorded type matches. This patch has been applied to the Linux kernel stable tree as commit 32bf7c6e01f5ba17a53ba236a770bd0274cefdf4 [1].
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2Patches
31ee147efee6832bf7c6e01f5bb160e791ab1Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
3News mentions
0No linked articles in our index yet.