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().
The gfs2_logd() function calls log flush functions gfs2_ail1_start(), gfs2_ail1_wait(), and gfs2_ail1_empty() without first acquiring the sdp->sd_log_flush_lock lock. Meanwhile, these functions require mutual exclusion with respect to concurrent transactions. Lack of this synchronization can result in race conditions that violate the consistency of internal kernel data structures. The fix introduces a __gfs2_log_flush() version without its own locking and requires acquiring the sdp->sd_log_flush_lock before calling the aforementioned functions.
An attacker or local user able to perform appropriate operations on a GFS2 file system can cause data corruption, system instability, or system failure (kernel panic). A high CVSS score (9.8) indicates potential ability to breach system confidentiality, integrity, and availability.
Apply patches available from the vendor according to references: https://git.kernel.org/stable/c/3b28eb75afe520972bacc833850c2b30aa0824cd and related commits. It is recommended to update the Linux kernel to a version containing the fix.
Linux kernel with GFS2 file system support; specific versions indicated in vendor references (patches available at git.kernel.org)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HLinux Kernel
OSLinux5.7 – 5.15.209 (excl.)5.16 – 6.1.175 (excl.)6.2 – 6.6.141 (excl.)6.7 – 6.12.91 (excl.)6.13 – 6.18.33 (excl.)6.19 – 7.0.10 (excl.)
Related vulnerabilities
Type confusion w V8 (Google Chrome) — zdalne uszkodzenie sterty
Commvault Command Center – nieuwierzytelniony RCE przez path traversal w ZIP
RCE przez YAML deserialization w IBM Aspera Faspex
RCE w VMware Workspace ONE Access i Identity Manager poprzez server-side template injection
Command Injection w VMware Workspace One Access i Identity Manager