CVE-2024-35953

In the Linux kernel, the following vulnerability has been resolved:

accel/ivpu: Fix deadlock in context_xa

ivpu_device->context_xa is locked both in kernel thread and IRQ context. It requires XA_FLAGS_LOCK_IRQ flag to be passed during initialization otherwise the lock could be acquired from a thread and interrupted by an IRQ that locks it for the second time causing the deadlock.

This deadlock was reported by lockdep and observed in internal tests.

Weakness

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

Affected Software

Extended Description

Locking is a type of synchronization behavior that ensures that multiple independently-operating processes or threads do not interfere with each other when accessing the same resource. All processes/threads are expected to follow the same steps for locking. If these steps are not followed precisely - or if no locking is done at all - then another process/thread could modify the shared resource in a way that is not visible or predictable to the original process. This can lead to data or memory corruption, denial of service, etc.

Potential Mitigations

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/25.html
• https://cwe.mitre.org/data/definitions/26.html
• https://cwe.mitre.org/data/definitions/27.html

References

• https://git.kernel.org/stable/c/d43e11d9c7fcb16f18bd46ab2556c2772ffc5775
• https://git.kernel.org/stable/c/e6011411147209bc0cc14628cbc155356837e52a
• https://git.kernel.org/stable/c/fd7726e75968b27fe98534ccbf47ccd6fef686f3
• https://git.kernel.org/stable/c/d43e11d9c7fcb16f18bd46ab2556c2772ffc5775
• https://git.kernel.org/stable/c/e6011411147209bc0cc14628cbc155356837e52a
• https://git.kernel.org/stable/c/fd7726e75968b27fe98534ccbf47ccd6fef686f3