gfs2: fix double destroy_workqueue error
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
gfs2: fix double destroy_workqueue error
When gfs2_fill_super() fails, destroy_workqueue() is called within gfs2_gl_hash_clear(), and the subsequent code path calls destroy_workqueue() on the same work queue again.
This issue can be fixed by setting the work queue pointer to NULL after the first destroy_workqueue() call and checking for a NULL pointer before attempting to destroy the work queue again.
From the CVE record · Linux
In the Linux kernel’s GFS2 code, a failure in gfs2_fill_super() can cause the same workqueue to be destroyed twice. The input does not specify how an attacker could trigger the failure or whether access or user interaction is required.
Engineers running Linux kernels with GFS2 should check their versions against the vendor advisory; affected versions were not provided.