gfs2: Fix possible data races in gfs2_show_options()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 48c2b613616235d7c97fda5982f50100a6c79166 · < a4f71523ed2123d63b431cc0cea4e9f363a0f054| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
gfs2: Fix possible data races in gfs2_show_options()
Some fields such as gt_logd_secs of the struct gfs2_tune are accessed without holding the lock gt_spin in gfs2_show_options():
val = sdp->sd_tune.gt_logd_secs; if (val != 30) seq_printf(s, ",commit=%d", val);
And thus can cause data races when gfs2_show_options() and other functions such as gfs2_reconfigure() are concurrently executed:
spin_lock(>->gt_spin); gt->gt_logd_secs = newargs->ar_commit;
To fix these possible data races, the lock sdp->sd_tune.gt_spin is acquired before accessing the fields of gfs2_tune and released after these accesses.
Further changes by Andreas:
From the CVE record · Linux
The Linux kernel's gfs2_show_options() reads tuning fields without holding the required lock, allowing data races when it runs concurrently with functions such as gfs2_reconfigure(). The input does not establish what an attacker could achieve or whether exploitation requires network access, authentication, or user interaction.
Engineers running the Linux kernel with GFS2 should check their installations; affected versions are not specified.