Erico Nunes

**Name of the Vulnerable Software and Affected Versions** Linux kernel versions prior to 6.6.43 **Description** The issue is related to the handling of shared interrupts in the Linux kernel's drm/lima component. When the driver is removed, the clocks are disabled early, but the interrupts remain registered until the end of the removal process. This can cause a crash if the driver is removed in a kernel with CONFIG DEBUG SHIRQ enabled. The problem arises because the interrupt handlers access device registers, which assume that the clocks are enabled. **Recommendations** To resolve the issue, update the Linux kernel to version 6.6.43 or later. As a temporary workaround, consider disabling the removal of the drm/lima driver in kernels with CONFIG DEBUG SHIRQ enabled until a patch is available.

**Name of the Vulnerable Software and Affected Versions** Linux kernel (affected versions not specified) **Description** The issue is related to a race condition in the Linux kernel's drm/lima component. This race condition can occur when a rendering job takes long enough to trigger the drm sched job timeout handler but still completes before the hard reset is done by the timeout handler. In some cases, this can result in a refcount imbalance on lima pm idle. The problem can be prevented by masking the irqs at the beginning of the timeout handler. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.