linux-kernel - Re: [PATCH v2] firmware: qcom: uefisecapp: Fix memory related IO errors and crashes

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: <171288524180.749915.6159719966958784520.b4-ty@kernel.org>
Date: Thu, 11 Apr 2024 20:27:24 -0500
From: Bjorn Andersson <andersson@...nel.org>
To: Maximilian Luz <luzmaximilian@...il.com>
Cc: Konrad Dybcio <konrad.dybcio@...aro.org>,
	Bartosz Golaszewski <brgl@...ev.pl>,
	Johan Hovold <johan+linaro@...nel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
	Guru Das Srinagesh <quic_gurus@...cinc.com>,
	Ard Biesheuvel <ardb@...nel.org>,
	linux-arm-msm@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	stable@...r.kernel.org
Subject: Re: [PATCH v2] firmware: qcom: uefisecapp: Fix memory related IO errors and crashes


On Sat, 06 Apr 2024 15:01:09 +0200, Maximilian Luz wrote:
> It turns out that while the QSEECOM APP_SEND command has specific fields
> for request and response buffers, uefisecapp expects them both to be in
> a single memory region. Failure to adhere to this has (so far) resulted
> in either no response being written to the response buffer (causing an
> EIO to be emitted down the line), the SCM call to fail with EINVAL
> (i.e., directly from TZ/firmware), or the device to be hard-reset.
> 
> [...]

Applied, thanks!

[1/1] firmware: qcom: uefisecapp: Fix memory related IO errors and crashes
      commit: ed09f81eeaa8f9265e1787282cb283f10285c259

Best regards,
-- 
Bjorn Andersson <andersson@...nel.org>