CVE-2024-56680: media: intel/ipu6: do not handle interrupts when device is disabled
In the Linux kernel, the following vulnerability has been resolved:
media: intel/ipu6: do not handle interrupts when device is disabled
Some IPU6 devices have shared interrupts. We need to handle properly case when interrupt is triggered from other device on shared irq line and IPU6 itself disabled. In such case we get 0xffffffff from ISRSTATUS register and handle all irq's cases, for what we are not not prepared and usually hang the whole system.
To avoid the issue use pmruntimegetifactive() to check if the device is enabled and prevent suspending it when we handle irq until the end of irq. Additionally use synchronizeirq() in suspend
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.22-1Fixed in 6.12.25-1 - Compensating control
In the Intel IPU6 interrupt and suspend handling, use pm_runtime_get_if_active() to verify that the device is enabled and prevent it from suspending while an IRQ is being handled; use synchronize_irq() during suspend, and handle shared-IRQ cases where IPU6 is disabled, including unexpected ISR_STATUS values such as 0xffffffff.
Event History
Frequently Asked Questions
What is the severity of CVE-2024-56680?
CVE-2024-56680 is considered a medium severity vulnerability due to its potential impact on system stability and security.
How do I fix CVE-2024-56680?
To fix CVE-2024-56680, update your Linux kernel to the latest version that includes the patch addressing this vulnerability.
Which systems are affected by CVE-2024-56680?
CVE-2024-56680 affects Intel Linux Kernel environments, particularly those utilizing IPU6 devices.
What are the risks of not addressing CVE-2024-56680?
Failing to address CVE-2024-56680 can lead to improper handling of interrupts which may impact device functionality and system performance.
Is there a workaround for CVE-2024-56680 before applying a patch?
Currently, there are no documented workarounds for CVE-2024-56680; applying the patch is the recommended solution.