linux-kernel - Re: [PATCH v6] misc: fastrpc: check qcom_scm_assign_mem() return in rpmsg

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2026012851-precut-apostle-1d38@gregkh>
Date: Wed, 28 Jan 2026 06:48:33 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Xingjing Deng <micro6947@...il.com>
Cc: srini@...nel.org, amahesh@....qualcomm.com, arnd@...db.de,
	dri-devel@...ts.freedesktop.org, linux-arm-msm@...r.kernel.org,
	linux-kernel@...r.kernel.org, Xingjing Deng <xjdeng@...a.edu.cn>,
	stable@...r.kernel.org
Subject: Re: [PATCH v6] misc: fastrpc: check qcom_scm_assign_mem() return in
 rpmsg_probe

On Wed, Jan 28, 2026 at 11:34:54AM +0800, Xingjing Deng wrote:
> In the SDSP probe path, qcom_scm_assign_mem() is used to assign the
> reserved memory to the configured VMIDs, but its return value was not checked.
> 
> Fail the probe if the SCM call fails to avoid continuing with an
> unexpected/incorrect memory permission configuration.
> 
> This issue was detected by a private static analysis tool.

As per our documentation, you need to say a bit more than this about
your tool.  Please read Documentation/process/researcher-guidelines.rst
for the details.

thanks,

greg k-h