dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53048

MEDIUM · 5.5 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 →
57/100
Remediation priority · Elevated
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: prevent NULL pointer dereference during unmount When flushing out outstanding glock work during an unmount, gfs2_log_flush() can be called when sdp->sd_jdesc has already been deallocated and sdp->sd_jdesc is NULL. Commit 35264909e9d1 ("gfs2: Fix NULL pointer dereference in gfs2_log_flush") added a check for that to gfs2_log_flush() itself, but it missed the sdp->sd_jdesc dereference in gfs2_log_release(). Fix that.

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 GFS2 filesystem, a NULL pointer dereference occurs in gfs2_log_release() during unmount. When sdp->sd_jdesc has already been deallocated (set to NULL), gfs2_log_release() still attempts to dereference it without checking first. A prior fix addressed this in gfs2_log_flush() but missed the same vulnerability in gfs2_log_release().

MitigationApply the kernel patch that adds a NULL check for sdp->sd_jdesc in gfs2_log_release() before dereferencing, similar to the existing check in gfs2_log_flush(). This is a single-point fix in the GFS2 logging subsystem.

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.15.200, < 5.15.209>= 6.1.162, < 6.1.175>= 6.6.37, < 6.6.141>= 6.9.8, < 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
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

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. Verify GFS2 filesystem is in use
    Check for mounted GFS2 filesystems using 'mount | grep gfs2' or check for GFS2 module loaded with 'lsmod | grep gfs2'
    Affected if GFS2 filesystem is mounted or the gfs2 module is loaded on the system
  2. Check running kernel version
    Run 'uname -r' to get the kernel version and compare it against the affected ranges: 5.15.200-5.15.208, 6.1.162-6.1.174, 6.6.37-6.6.140, 6.9.8-6.12.90, 6.13-6.18.32, 6.19-7.0.9
    Affected if The kernel version falls within any of the affected ranges listed
  3. Check for GFS2 mount activity
    Review any mounted GFS2 filesystems with 'findmnt -t gfs2' and check system logs for recent unmount activity
    Affected if GFS2 filesystems have been recently unmounted on affected kernel versions, which could trigger the NULL dereference
  4. Verify patch presence in kernel
    If kernel source or debug symbols are available, inspect gfs2_log_release() in fs/gfs2/log.c for NULL check on sdp->sd_jdesc before dereferencing
    Affected if The NULL check is missing in gfs2_log_release(), indicating the vulnerability is present

The system is affected if it runs a vulnerable kernel version from the affected ranges AND uses GFS2 filesystems that undergo unmount operations.

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.

dbcve · scoped
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 that adds a NULL check for sdp->sd_jdesc in gfs2_log_release() before dereferencing, similar to the existing check in gfs2_log_flush(). This is a single-point fix in the GFS2 logging subsystem.

Recommended fix High confidence

Linux Kernel 5.15.209, 6.1.175, 6.6.141, or 6.12.91 (depending on which branch you are on)

  1. Identify the currently running kernel version using `uname -r`
  2. Determine which version range your current kernel falls into (5.15.200-5.15.208, 6.1.162-6.1.174, 6.6.37-6.6.140, or 6.9.8-6.12.90)
  3. Upgrade the Linux kernel to the fixed version for your branch: 5.15.209 for 5.15.x, 6.1.175 for 6.1.x, 6.6.141 for 6.6.x, or 6.12.91 for 6.9.x-6.12.x
  4. Reboot the system to load the patched kernel
  5. Verify the fix is applied by checking `uname -r` matches the fixed version
Caveat Standard kernel upgrade risks apply - ensure compatibility with custom modules and drivers before deploying in production

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

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA3.0 h
10.0 hours of engineering $1,700
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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