Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-53048gfs2: prevent NULL pointer dereference during unmount

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.

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-53048, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected c3c5cfa3170c0940bc66a142859caac07d19b9d6 – < cec55674354794eddb80b914f73a6bf9b7fc304a
    • affected 5f6a84cfb33b34610623857bd93919dcb661e29b – < 2fc4c868c9060f424fd4a7cacb0aec5082aba4de
    • affected 3429ef5f50909cee9e498c50f0c499b9397116ce – < 233a0945a4b1dbe3f38c30afb7d05b76c67f1193
    • affected 35264909e9d1973ab9aaa2a1b07cda70f12bb828 – < e15f16761594e80b15776980b27c35477655a135
    • affected 35264909e9d1973ab9aaa2a1b07cda70f12bb828 – < d8ffae016c4a78693fe1283335d0b6833a9c1366
    • affected 35264909e9d1973ab9aaa2a1b07cda70f12bb828 – < abd73229f0e886a91a16ea781ab656bd9b4d1ee8
    • affected 35264909e9d1973ab9aaa2a1b07cda70f12bb828 – < 74b4dbb946060a3233604d91859a9abd3708141d
    • affected f54f9d5368a4e92ede7dd078a62788dae3a7c6ef
    • affected 5.15.200 – < 5.15.209
    • affected 6.1.162 – < 6.1.175
    • affected 6.6.37 – < 6.6.141
    • affected 6.9.8 – < 6.10
  • Linux · Linux

    • affected 6.10
    • unaffected < 6.10
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.141 – ≤ 6.6.*
    • unaffected 6.12.91 – ≤ 6.12.*
    • unaffected 6.18.33 – ≤ 6.18.*
    • unaffected 7.0.10 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-53048 badge
[![CVE-2026-53048](https://cveledger.app/badge/CVE-2026-53048.svg)](https://cveledger.app/cve/CVE-2026-53048)

Record last updated .