linux-cve-announce - CVE-2023-53622: gfs2: Fix possible data races in gfs2_show

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025100710-CVE-2023-53622-2f9b@gregkh>
Date: Tue,  7 Oct 2025 17:19:27 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53622: gfs2: Fix possible data races in gfs2_show_options()

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

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->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:

- Don't hold the spin lock over the seq_printf operations.

The Linux kernel CVE team has assigned CVE-2023-53622 to this issue.


Affected and fixed versions
===========================

	Fixed in 4.14.324 with commit 7e5bbeb7eb813bb2568e1d5d02587df943272e57
	Fixed in 4.19.293 with commit 235a5ae73cea29109a3e06f100493f17857e6a93
	Fixed in 5.4.255 with commit b4a7ab57effbed42624842f2ab2a49b177c21a47
	Fixed in 5.10.192 with commit 7c5b2649f6a37d45bfb7abf34c9b71d08677139f
	Fixed in 5.15.128 with commit 85e888150075cb221270b64bf772341fc6bd11d9
	Fixed in 6.1.47 with commit a4f71523ed2123d63b431cc0cea4e9f363a0f054
	Fixed in 6.4.12 with commit 42077d4de49e4d9c773c97c42d5383b4899a8f9d
	Fixed in 6.5 with commit 6fa0a72cbbe45db4ed967a51f9e6f4e3afe61d20

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2023-53622
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	fs/gfs2/super.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/7e5bbeb7eb813bb2568e1d5d02587df943272e57
	https://git.kernel.org/stable/c/235a5ae73cea29109a3e06f100493f17857e6a93
	https://git.kernel.org/stable/c/b4a7ab57effbed42624842f2ab2a49b177c21a47
	https://git.kernel.org/stable/c/7c5b2649f6a37d45bfb7abf34c9b71d08677139f
	https://git.kernel.org/stable/c/85e888150075cb221270b64bf772341fc6bd11d9
	https://git.kernel.org/stable/c/a4f71523ed2123d63b431cc0cea4e9f363a0f054
	https://git.kernel.org/stable/c/42077d4de49e4d9c773c97c42d5383b4899a8f9d
	https://git.kernel.org/stable/c/6fa0a72cbbe45db4ed967a51f9e6f4e3afe61d20