Rodrigo Vivi

Name of the Vulnerable Software and Affected Versions: Linux kernel (affected versions not specified) Description: The issue concerns the use of spin lock/unlock() functions in interrupt contexts, which could result in a deadlock when an interrupt occurs while holding a lock, as seen in GitLab issue #13399. To address this, the solution involves saving the irq state before spin lock acquisition, using spin lock irqsave() in interruptible contexts, and adding irqs' state save/restore calls to all locks/unlocks in signal irq work() execution. Recommendations: At the moment, there is no information about a newer version that contains a fix for this vulnerability.

A vulnerability has been resolved in the Linux kernel, specifically in the drm/xe component, where an opregion leak was fixed. The issue was related to the setup and cleanup of the display, which ideally should be done by the display itself. However, this requires a bigger refactor to be done on both i915 and xe. For now, the leak has been fixed. The vulnerability was related to an unreferenced object, and a backtrace is provided, showing the functions involved, including `kmemleak alloc`, `kmalloc trace noprof`, `intel opregion setup`, and others.

A refcount leak issue in the Linux kernel has been identified and resolved. The problem occurs in the `intel dp add mst connector()` function, where a reference count leak can happen if `drm connector init` fails. To address this, it is necessary to drop the refcount of the port before calling `intel connector free` to ensure proper cleanup.