dbcve.org
Linux KernelOperating system · Linux

CVE-2023-53622

HIGH · 7.0 CVSS v3.1 Published 2025-10-07
Fix available
A fix is available. Upgrade to 4.14.324 / 4.19.293 or later.
See remediation →
72/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
In the Linux kernel, the following vulnerability has been resolved: gfs2: Fix possible data races in gfs2_show_options() Some fields such as gt_logd_secs of the struct gfs2_tune are accessed without holding the lock gt_spin in gfs2_show_options(): val = sdp->sd_tune.gt_logd_secs; if (val != 30) seq_printf(s, ",commit=%d", val); And thus can cause data races when gfs2_show_options() and other functions such as gfs2_reconfigure() are concurrently executed: spin_lock(&gt->gt_spin); gt->gt_logd_secs = newargs->ar_commit; To fix these possible data races, the lock sdp->sd_tune.gt_spin is acquired before accessing the fields of gfs2_tune and released after these accesses. Further changes by Andreas: - Don't hold the spin lock over the seq_printf operations.

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-362

Two operations that should be atomic can interleave, so an attacker who wins a narrow timing window reaches an inconsistent, exploitable state. These bugs are subtle and easy to miss in review. Fixing them properly means correct locking or atomic operations around the shared resource.

General guidance for the race condition 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
Linux KernelOperating system
Affected:>= 2.6.31, < 4.14.324>= 4.15, < 4.19.293>= 4.20, < 5.4.255>= 5.5, < 5.10.192>= 5.11, < 5.15.128>= 5.16, < 6.1.47>= 6.2, < 6.4.12

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/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 4.14.324 / 4.19.293 / 5.4.255 or later
Fixed in 4.14.3244.19.2935.4.255
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to Linux kernel 4.14.324+, 4.19.293+, 5.4.255+, or 5.10.192+ depending on your current branch

  1. Identify the current running Linux kernel version using `uname -r`
  2. Determine which version range the current kernel falls into (4.14.x, 4.19.x, 5.4.x, or 5.10.x)
  3. For 4.14.x kernels: upgrade to kernel version 4.14.324 or later
  4. For 4.19.x kernels: upgrade to kernel version 4.19.293 or later
  5. For 5.4.x kernels: upgrade to kernel version 5.4.255 or later
  6. For 5.10.x kernels: upgrade to kernel version 5.10.192 or later
  7. Alternatively, apply the vendor patch from commit 235a5ae73cea29109a3e06f100493f17857e6a93 which adds spin_lock(&gt->gt_spin) before accessing gt_logd_secs and other gfs2_tune fields in gfs2_show_options(), then releases the lock after the accesses
  8. Reboot into the updated kernel and verify the GFS2 module loads without errors
Caveat Major kernel upgrades may require rebuilding out-of-tree kernel modules; ensure compatibility of dependent software with the new kernel version

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,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-53622 — 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-2023-53622 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