gfs2: Fix NULL pointer dereference in gfs2_log_flush
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
gfs2: Fix NULL pointer dereference in gfs2_log_flush
In gfs2_jindex_free(), set sdp->sd_jdesc to NULL under the log flush lock to provide exclusion against gfs2_log_flush().
In gfs2_log_flush(), check if sdp->sd_jdesc is non-NULL before dereferencing it. Otherwise, we could run into a NULL pointer dereference when outstanding glock work races with an unmount (glock_work_func -> run_queue -> do_xmote -> inode_go_sync -> gfs2_log_flush).
From the CVE record · Linux
The Linux kernel’s GFS2 log flush can dereference a NULL pointer when outstanding glock work races with an unmount. The input does not specify how an attacker could trigger this condition or whether authentication or user interaction is required.
Teams running Linux kernels with GFS2 should check their versions against the vendor advisory; affected versions are not specified in the input.