gfs2: No more self recovery
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 601ef0d52e9617588fcff3df26953592f2eb44ac · < 97c94c7dbddc34d353c83b541b3decabf98d04af| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
gfs2: No more self recovery
When a node withdraws and it turns out that it is the only node that has the filesystem mounted, gfs2 currently tries to replay the local journal to bring the filesystem back into a consistent state. Not only is that a very bad idea, it has also never worked because gfs2_recover_func() will refuse to do anything during a withdraw.
However, before even getting to this point, gfs2_recover_func() dereferences sdp->sd_jdesc->jd_inode. This was a use-after-free before commit 04133b607a78 ("gfs2: Prevent double iput for journal on error") and is a NULL pointer dereference since then.
Simply get rid of self recovery to fix that.
From the CVE record · Linux
The Linux kernel’s gfs2 self-recovery path dereferences a NULL pointer when a node withdraws while it is the only node with the filesystem mounted. Before commit 04133b607a78, the same operation caused a use-after-free. The input does not establish whether an attacker can trigger the condition or what access would be required.
Engineers running Linux kernels with gfs2 should check their kernel against the vendor advisory; affected versions are not specified.