CVE-2026-53048
gfs2: prevent NULL pointer dereference during unmount
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.15.209, 6.1.175, 6.6.141, 6.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
- CVE published
Affected versions
- Linux Linux
From 5.15.200 · fixed in 5.15.209; From 6.1.162 · fixed in 6.1.175; From 6.6.37 · fixed in 6.6.141; From 6.9.8 · fixed in 6.10
- Linux Linux
6.10
References 7
git.kernel.org
- stable/c/cec55674354794eddb80b914f73a6bf9b7fc304a
- stable/c/2fc4c868c9060f424fd4a7cacb0aec5082aba4de
- stable/c/233a0945a4b1dbe3f38c30afb7d05b76c67f1193
- stable/c/e15f16761594e80b15776980b27c35477655a135
- stable/c/d8ffae016c4a78693fe1283335d0b6833a9c1366
- stable/c/abd73229f0e886a91a16ea781ab656bd9b4d1ee8
- stable/c/74b4dbb946060a3233604d91859a9abd3708141d