gfs2: prevent NULL pointer dereference during unmount
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 35264909e9d1973ab9aaa2a1b07cda70f12bb828 · < abd73229f0e886a91a16ea781ab656bd9b4d1ee8| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's gfs2 code can dereference a NULL pointer while flushing outstanding work during unmount, after the journal descriptor has been deallocated. This can cause a crash; the input does not specify whether an attacker can trigger it or what access would be required.
Anyone running a Linux kernel with gfs2 should check their kernel version; affected versions are not specified.