dbcve.org
MariaDBDatabase / datastore

CVE-2022-31621

MEDIUM · 5.5 CVSS v3.1 Published 2022-05-25
Fix available
A fix is available. Upgrade to 10.2.41 / 10.3.32 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
MariaDB Server before 10.7 is vulnerable to Denial of Service. In extra/mariabackup/ds_xbstream.cc, when an error occurs (stream_ctxt->dest_file == NULL) while executing the method xbstream_open, 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-667

Shared resources are accessed without correct locking, so concurrent operations interleave into inconsistent — and sometimes exploitable — states, or deadlock the service outright. These bugs are subtle and timing-dependent. The fix is correct, consistent locking or atomic operations around every shared resource.

General guidance for the improper locking class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MariaDBDatabase / datastore
Affected:< 10.2.41>= 10.3.0, < 10.3.32>= 10.4.0, < 10.4.22>= 10.5.0, < 10.5.13>= 10.6.0, < 10.6.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.2.41 / 10.3.32 / 10.4.22 or later
Fixed in 10.2.4110.3.3210.4.22
Vendor patch github.com →
Recommended fix High confidence

Upgrade to MariaDB 10.2.41 / 10.3.32 / 10.4.22 / 10.5.13 or later (10.6.x or 10.7.x recommended)

  1. 1. Identify the current MariaDB Server version by running: `mysql --version` or `mariadb --version`
  2. 2. Based on the current version branch, plan upgrade to the minimum fixed version: 10.2.41, 10.3.32, 10.4.22, or 10.5.13 (or a later stable release)
  3. 3. Before upgrading, backup all databases using mysqldump or mariabackup
  4. 4. Stop the MariaDB service: `systemctl stop mariadb` or `service mariadb stop`
  5. 5. Upgrade MariaDB packages using your package manager (e.g., `apt-get update && apt-get install mariadb-server` or `yum update mariadb-server`)
  6. 6. Start the MariaDB service: `systemctl start mariadb` or `service mariadb start`
  7. 7. Verify the new version is running: `mysql --version`
  8. 8. Run mysql_upgrade to ensure all system tables are current
Caveat Standard MariaDB upgrade considerations apply - review release notes for breaking changes between your current version and target version, particularly for replication and stored procedures

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-31621 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-31621 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data