linux-cve-announce - CVE-2026-23071: regmap: Fix race condition in hwspinlock irqsave routine

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: <2026020418-CVE-2026-23071-675b@gregkh>
Date: Wed,  4 Feb 2026 17:14:30 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2026-23071: regmap: Fix race condition in hwspinlock irqsave routine

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

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

In the Linux kernel, the following vulnerability has been resolved:

regmap: Fix race condition in hwspinlock irqsave routine

Previously, the address of the shared member '&map->spinlock_flags' was
passed directly to 'hwspin_lock_timeout_irqsave'. This creates a race
condition where multiple contexts contending for the lock could overwrite
the shared flags variable, potentially corrupting the state for the
current lock owner.

Fix this by using a local stack variable 'flags' to store the IRQ state
temporarily.

The Linux kernel CVE team has assigned CVE-2026-23071 to this issue.


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

	Issue introduced in 4.15 with commit 8698b9364710e7bac84b3af07dd410e39c8c2e08 and fixed in 6.6.122 with commit 24f31be6ad70537fd7706269d99c92cade465a09
	Issue introduced in 4.15 with commit 8698b9364710e7bac84b3af07dd410e39c8c2e08 and fixed in 6.12.68 with commit 4aab0ca0a0f7760e33edcb4e47576064d05128f5
	Issue introduced in 4.15 with commit 8698b9364710e7bac84b3af07dd410e39c8c2e08 and fixed in 6.18.8 with commit c2d2cf710dc3ee1a69e00b4ed8de607a92a07889
	Issue introduced in 4.15 with commit 8698b9364710e7bac84b3af07dd410e39c8c2e08 and fixed in 6.19-rc7 with commit 4b58aac989c1e3fafb1c68a733811859df388250

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-2026-23071
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:
	drivers/base/regmap/regmap.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/24f31be6ad70537fd7706269d99c92cade465a09
	https://git.kernel.org/stable/c/4aab0ca0a0f7760e33edcb4e47576064d05128f5
	https://git.kernel.org/stable/c/c2d2cf710dc3ee1a69e00b4ed8de607a92a07889
	https://git.kernel.org/stable/c/4b58aac989c1e3fafb1c68a733811859df388250