A denial of service vulnerability was found in tipc_crypto_key_revoke in net/tipc/crypto.c in the Linux kernel’s TIPC subsystem. This flaw allows guests with local user privileges to trigger a deadlock and potentially crash the system.
The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Linux_kernel | Linux | * | 6.6 (excluding) |
| Linux_kernel | Linux | 6.6-rc1 (including) | 6.6-rc1 (including) |
| Linux_kernel | Linux | 6.6-rc2 (including) | 6.6-rc2 (including) |
| Linux_kernel | Linux | 6.6-rc3 (including) | 6.6-rc3 (including) |
| Linux_kernel | Linux | 6.6-rc4 (including) | 6.6-rc4 (including) |
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.