linux-kernel - Re: [PATCH v2 0/4] firmware: qcom: scm: fix potential race condition with tzmem

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMRc=MepAV4iHvGbBKmrq1NevC9OBZ1z=JBP-AQWhJzZusK02w@mail.gmail.com>
Date: Fri, 11 Jul 2025 09:52:04 +0200
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Bjorn Andersson <andersson@...nel.org>, Konrad Dybcio <konradybcio@...nel.org>, 
	Johan Hovold <johan@...nel.org>
Cc: linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org, 
	Bartosz Golaszewski <bartosz.golaszewski@...aro.org>, 
	Konrad Dybcio <konrad.dybcio@....qualcomm.com>, Johan Hovold <johan+linaro@...nel.org>
Subject: Re: [PATCH v2 0/4] firmware: qcom: scm: fix potential race condition
 with tzmem

On Mon, Jun 30, 2025 at 2:12 PM Bartosz Golaszewski <brgl@...ev.pl> wrote:
>
> There's a race condition between the SCM call API consumers and the TZMem
> initialization in the SCM firmware driver. The internal __scm pointer is
> assigned - marking SCM as ready for accepting calls - before the tzmem
> memory pool is fully initialized. While the race is unlikely to be hit
> thanks to the SCM driver being initialized early, it still must be
> addressed.
>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
> ---

We're late into rc5 so gentle ping, any chance we could get this
queued for v6.17?

Bartosz