gfs2: add some missing log locking
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5e4c7632aae1cce137792647f4fb6f599d1da893 · < 98e8bf249c790d56de1abc4a5f8bd68035a00921| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
gfs2: add some missing log locking
Function gfs2_logd() calls the log flushing functions gfs2_ail1_start(), gfs2_ail1_wait(), and gfs2_ail1_empty() without holding sdp->sd_log_flush_lock, but these functions require exclusion against concurrent transactions.
To fix that, add a non-locking __gfs2_log_flush() function. Then, in gfs2_logd(), take sdp->sd_log_flush_lock before calling the above mentioned log flushing functions and __gfs2_log_flush().
From the CVE record · Linux
The Linux kernel's gfs2_logd() calls log-flushing functions without a lock required to exclude concurrent transactions. This can allow a race with those transactions; the input does not specify how an attacker could trigger it or whether authentication or user interaction is required.
Engineers running Linux systems that use gfs2 should check their kernel versions; affected versions are not specified.