NULL Pointer Dereference in GFS2 Filesystem

Publication date: 2026-06-24

Last updated on: 2026-07-14

Assigner: kernel.org

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-06-24

Last Modified

2026-07-14

Generated

2026-07-15

AI Q&A

2026-06-24

EPSS Evaluated

2026-07-13

NVD

CVE-2026-53048

EUVD

EUVD-2026-38916

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Impact Analysis

The vulnerability can cause a NULL pointer dereference during the unmounting of the gfs2 filesystem, which may lead to a kernel crash or system instability. This can result in denial of service or unexpected system behavior when the affected code path is executed.

Executive Summary

This vulnerability exists in the Linux kernel's gfs2 filesystem code. It involves a NULL pointer dereference during the unmount process. Specifically, when flushing outstanding glock work during unmount, the function gfs2_log_flush() can be called after the sdp->sd_jdesc pointer has already been deallocated and set to NULL. Although a previous fix added a check in gfs2_log_flush() to prevent this, it missed a similar dereference in the gfs2_log_release() function, which this vulnerability addresses.

Hi! I’m here to help you understand CVE-2026-53048. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70