dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53049

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 5.15.209 / 6.1.175 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 8 weeks old

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: add some missing log locking Function gfs2_logd() calls the log flushing functions gfs2_ail1_start(), gfs2_ail1_wait(), and gfs2_ail1_empty() without holding sdp->sd_log_flush_lock, but these functions require exclusion against concurrent transactions. To fix that, add a non-locking __gfs2_log_flush() function. Then, in gfs2_logd(), take sdp->sd_log_flush_lock before calling the above mentioned log flushing functions and __gfs2_log_flush().

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 · high confidence

In the Linux kernel's GFS2 filesystem, the gfs2_logd() function calls log flushing functions (gfs2_ail1_start, gfs2_ail1_wait, gfs2_ail1_empty) without holding the required sdp->sd_log_flush_lock, creating a race condition where concurrent transactions can interfere with log flushing operations. The fix introduces a non-locking __gfs2_log_flush() internal function and ensures gfs2_logd() acquires the lock before performing these operations.

MitigationApply the kernel patch to add proper locking in gfs2_logd() before calling log flushing functions, ensuring atomic exclusion against concurrent transactions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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:>= 5.7, < 5.15.209>= 5.16, < 6.1.175>= 6.2, < 6.6.141>= 6.7, < 6.12.91>= 6.13, < 6.18.33>= 6.19, < 7.0.10

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

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if GFS2 filesystems are mounted
    Run 'mount -t gfs2' or 'grep gfs2 /proc/mounts' to list mounted GFS2 filesystems
    Affected if No GFS2 filesystems are mounted means the system is not affected by this vulnerability
  2. Check the running kernel version
    Run 'uname -r' to get the kernel version, then compare it to the version that includes the fix for this CVE (the patch introduces __gfs2_log_flush() and adds sd_log_flush_lock protection)
    Affected if Running an unpatched kernel version where gfs2_logd() lacks the required lock protection
  3. Verify GFS2 kernel module is loaded
    Run 'lsmod | grep gfs2' to confirm the GFS2 module is loaded
    Affected if GFS2 module is loaded and the kernel version is unpatched
  4. Examine gfs2_logd source code if accessible
    Check the source file fs/gfs2/log.c for the gfs2_logd() function and verify whether sdp->sd_log_flush_lock is held before calling gfs2_ail1_start, gfs2_ail1_wait, or gfs2_ail1_empty
    Affected if The source code shows these functions are called without holding the lock (vulnerable state)

A system is affected only if it has mounted GFS2 filesystems running on an unpatched kernel where gfs2_logd() calls log flushing functions without holding sdp->sd_log_flush_lock.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to 5.15.209 / 6.1.175 / 6.6.141 or later
Fixed in 5.15.2096.1.1756.6.141
Interim mitigation

Apply the kernel patch to add proper locking in gfs2_logd() before calling log flushing functions, ensuring atomic exclusion against concurrent transactions.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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