linux-kernel - Re: [PATCH] arm64/gcs: Flush the GCS locking state on exec

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: <176582226393.1756467.9855121048488078844.b4-ty@arm.com>
Date: Mon, 15 Dec 2025 18:17:37 +0000
From: Catalin Marinas <catalin.marinas@....com>
To: Will Deacon <will@...nel.org>,
	Thiago Jung Bauermann <thiago.bauermann@...aro.org>,
	Mark Brown <broonie@...nel.org>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Yury Khrustalev <Yury.Khrustalev@....com>
Subject: Re: [PATCH] arm64/gcs: Flush the GCS locking state on exec

On Sat, 29 Nov 2025 00:48:45 +0000, Mark Brown wrote:
> When we exec a new task we forget to flush the set of locked GCS mode bits.
> Since we do flush the rest of the state this means that if GCS is locked
> the new task will be unable to enable GCS, it will be locked as being
> disabled. Add the expected flush.
> 
> 

Applied to arm64 (for-next/fixes), thanks!

[1/1] arm64/gcs: Flush the GCS locking state on exec
      https://git.kernel.org/arm64/c/98a97bf41528

-- 
Catalin