In MariaDB before 10.9.2, compress_write in extra/mariabackup/ds_compress.cc does not release data_mutex upon a stream write failure, which allows local users to trigger a deadlock.
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 |
|---|---|---|---|
| Mariadb | Mariadb | 10.3.0 (including) | 10.3.36 (excluding) |
| Mariadb | Mariadb | 10.4.0 (including) | 10.4.26 (excluding) |
| Mariadb | Mariadb | 10.5.0 (including) | 10.5.17 (excluding) |
| Mariadb | Mariadb | 10.6.0 (including) | 10.6.9 (excluding) |
| Mariadb | Mariadb | 10.7.0 (including) | 10.7.5 (excluding) |
| Mariadb | Mariadb | 10.8.0 (including) | 10.8.4 (excluding) |
| Mariadb | Mariadb | 10.9.1 (including) | 10.9.1 (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.