MariaDB Server before 10.7 is vulnerable to Denial of Service. In extra/mariabackup/ds_compress.cc, when an error occurs (pthread_create returns a nonzero value) while executing the method create_worker_threads, the held lock is not released correctly, which allows local users to trigger a denial of service due to the deadlock. Note: The vendor argues this is just an improper locking bug and not a vulnerability with adverse effects.
Weakness
The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Mariadb | Mariadb | * | 10.2.42 (excluding) |
| Mariadb | Mariadb | 10.3.0 (including) | 10.3.33 (excluding) |
| Mariadb | Mariadb | 10.4.0 (including) | 10.4.23 (excluding) |
| Mariadb | Mariadb | 10.5.0 (including) | 10.5.14 (excluding) |
| Mariadb | Mariadb | 10.6.0 (including) | 10.6.6 (excluding) |
| Mariadb | Mariadb | 10.7.0 (including) | 10.7.2 (excluding) |
| Red Hat Enterprise Linux 8 | RedHat | mariadb:10.5-8060020220614163302.ad008a3a | * |
| Red Hat Enterprise Linux 8 | RedHat | mariadb:10.3-8060020220715055054.ad008a3a | * |
| Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support | RedHat | mariadb:10.5-8040020231006044227.522a0ee4 | * |
| Red Hat Enterprise Linux 8.4 Telecommunications Update Service | RedHat | mariadb:10.5-8040020231006044227.522a0ee4 | * |
| Red Hat Enterprise Linux 8.4 Update Services for SAP Solutions | RedHat | mariadb:10.5-8040020231006044227.522a0ee4 | * |
| Red Hat Enterprise Linux 9 | RedHat | mariadb-3:10.5.16-2.el9_0 | * |
| Red Hat Software Collections for Red Hat Enterprise Linux 7 | RedHat | rh-mariadb105-mariadb-3:10.5.16-2.el7 | * |
| Red Hat Software Collections for Red Hat Enterprise Linux 7 | RedHat | rh-mariadb103-mariadb-3:10.3.35-1.el7 | * |
| Mariadb-10.1 | Ubuntu | bionic | * |
| Mariadb-10.5 | Ubuntu | impish | * |
| Mariadb-10.6 | Ubuntu | kinetic | * |
| Mariadb-10.6 | Ubuntu | lunar | * |
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://github.com/MariaDB/server/commit/e1eb39a446c30b8459c39fd7f2ee1c55a36e97d2
- https://jira.mariadb.org/browse/MDEV-26561
- https://jira.mariadb.org/browse/MDEV-26561?filter=-2
- https://jira.mariadb.org/browse/MDEV-26574
- https://security.netapp.com/advisory/ntap-20220707-0006/
- https://github.com/MariaDB/server/commit/e1eb39a446c30b8459c39fd7f2ee1c55a36e97d2
- https://jira.mariadb.org/browse/MDEV-26561
- https://jira.mariadb.org/browse/MDEV-26561?filter=-2
- https://jira.mariadb.org/browse/MDEV-26574
- https://security.netapp.com/advisory/ntap-20220707-0006/