CVE Vulnerabilities

CVE-2022-31623

Improper Locking

Published: May 25, 2022 | Modified: May 17, 2024
CVSS 3.x
5.5
MEDIUM
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
2.1 LOW
AV:L/AC:L/Au:N/C:N/I:N/A:P
RedHat/V2
RedHat/V3
5.5 MODERATE
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Ubuntu
MEDIUM

MariaDB Server before 10.7 is vulnerable to Denial of Service. In extra/mariabackup/ds_compress.cc, when an error occurs (i.e., going to the err label) while executing the method create_worker_threads, the held lock thd->ctrl_mutex 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 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

References