linux-kernel - Re: [PATCH v2] 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>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <176825519481.237017.5137209377182553330.b4-ty@kernel.org>
Date: Mon, 12 Jan 2026 21:59:54 +0000
From: Mark Brown <broonie@...nel.org>
To: gregkh@...uxfoundation.org, rafael@...nel.org, dakr@...nel.org, 
 baolin.wang@...ux.alibaba.com, cylee12@...ltek.com, 
 Yu-Chun Lin <eleanor.lin@...ltek.com>
Cc: linux-kernel@...r.kernel.org, james.tai@...ltek.com, 
 cy.huang@...ltek.com, stanley_chang@...ltek.com
Subject: Re: [PATCH v2] regmap: Fix race condition in hwspinlock irqsave
 routine

On Wed, 07 Jan 2026 11:26:10 +0800, Yu-Chun Lin wrote:
> 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.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next

Thanks!

[1/1] regmap: Fix race condition in hwspinlock irqsave routine
      commit: 4b58aac989c1e3fafb1c68a733811859df388250

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark